Read and write Folk CRM people, companies, groups and notes. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"folk": {
"url": "https://folk.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"folk": {
"type": "http",
"url": "https://folk.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Folk API key.
Create one in Folk → Settings → API keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Folk API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Folk connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
folk_get_current_user | read | Get current user Get the user associated with the current Folk API key. Folk REST: GET /v1/users/me. |
folk_list_users | read | List users List users in the Folk workspace (id, name, email) — useful for resolving owner ids. Folk REST: GET /v1/users. |
folk_list_people | read | List people List/filter people (contacts). Supports cursor pagination and structured filters. Folk REST: GET /v1/people. |
folk_get_person | read | Get person Get a single person (contact) by id. Folk REST: GET /v1/people/{id}. |
folk_list_companies | read | List companies List/filter companies. Supports cursor pagination and structured filters. Folk REST: GET /v1/companies. |
folk_get_company | read | Get company Get a single company by id. Folk REST: GET /v1/companies/{id}. |
folk_list_groups | read | List groups List groups in the Folk workspace (ids needed to place people/companies). Folk REST: GET /v1/groups. |
folk_list_notes | read | List notes List notes, optionally scoped to an entity or filtered by full text and creation date. Folk REST: GET /v1/notes. |
folk_get_note | read | Get note Get a single note by id. Folk REST: GET /v1/notes/{id}. |
folk_create_person | write | Create person Create a new person (contact). All fields are optional. Folk REST: POST /v1/people. |
folk_update_person | write | Update person Update fields on an existing person. Only provided fields are changed; list-valued fields (emails, phones, groups, companies, etc.) REPLACE the existing values. Folk REST: PATCH /v1/people/{id}. |
folk_create_company | write | Create company Create a new company. `name` is required. Folk REST: POST /v1/companies. |
folk_update_company | write | Update company Update fields on an existing company. Only provided fields are changed; list-valued fields REPLACE the existing values. Folk REST: PATCH /v1/companies/{id}. |
folk_create_note | write | Create note Create a note attached to an entity (person/company). Folk REST: POST /v1/notes. |
folk_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
folk_request_feature | Request a missing feature Tell usefulapi that the user needs something the Folk tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
folk_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Folk tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
folk_cancel_subscription | Cancel the Pro subscription Cancel the caller's Folk Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run folk_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Folk server only. Subscribe with folk_upgrade (it returns a Stripe Checkout link). Cancel any time with folk_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running folk_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Folk. The server calls the Folk API with your own Folk access, so it sees only the data that your account can see.
The login page asks for your Folk API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Folk API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Folk API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Folk.
Yes, if you approve it. 5 of the 14 Folk tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Folk server only. Run folk_usage_status to see how many calls you used.
Ask the AI to run folk_upgrade: it returns a Stripe Checkout link. To cancel, run folk_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with folk_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.