MCP server Pro

Tylode's MCP server lets AI assistants that support the Model Context Protocol (Claude, Cursor, VS Code and many others) work with your Tylode: search it, read pages, create and move cards, add rows to a database, change events, answer chats and send internal mail, all by asking in plain language.

#What it gives you

• 53 tools covering workspaces, pages, databases, boards, calendar, whiteboards, presentations, search, chats, internal mail, My drive and notifications.
• The same access as you. The assistant sees exactly what you can see in the app and nothing more, because every tool calls the REST API with your token.
• No code. You add the server to your assistant once, then ask things like "What's on my calendar this week?".

#Requirements

• An account on Pro or Premium. The plan is checked on every request.
• From Claude or ChatGPT, nothing else: you sign in with your Tylode account (see Claude and ChatGPT, nothing to install).
• From other clients, a personal access token. Create one in Settings → API and webhooks → API and plugins → Personal access tokens (see Authentication). Give it a name like "Local MCP" so you can recognize and revoke it later.

#URL and transport

Responses come back as plain JSON rather than a stream. Clients that only speak stdio can connect through the mcp-remote bridge, shown below.

#Set it up

#Claude and ChatGPT, nothing to install

All you need is the address https://app.tylode.com/api/mcp:

• Claude (web, desktop and mobile): in Settings → Connectors, add a custom connector, name it Tylode and paste the address.
• ChatGPT: in the Connectors (or Apps) settings, create a new one with that address and OAuth authentication. Depending on your plan, ChatGPT may ask you to turn on developer mode first.

When you connect, Tylode opens: sign in with your account (if you weren't already), review the permissions the assistant asks for and click Authorize. The screen tells you which domain you'll return to (claude.ai, chatgpt.com…): if it isn't the one of the assistant you just connected, cancel.

The assistant only sees the tools for the permissions you authorize. The delete permissions appear separately, under It can also delete, unticked: the assistant can only delete what you tick. If you connected it before some permissions existed (such as databases, uploading files to My drive or deleting), it keeps the ones you authorized back then: to give it the new ones, disconnect it, connect it again and authorize it again. Until then, it can't change cards, whiteboard elements or what's inside slides either (those permissions used to only allow creating): it'll ask you to connect it again. You can remove its access at any time in Settings → API and webhooks → API and plugins → Applications connected to your account.

#With a personal token

In every example, replace tylode_pat_xxx with your token. When the client lets you read it from an environment variable, do that instead of writing the token in the file.

#Claude Code

Run:

claude mcp add --transport http tylode https://app.tylode.com/api/mcp --header "Authorization: Bearer tylode_pat_xxx"

This adds it to the current project. Add --scope user to have it in all your projects. Then run /mcp inside Claude Code to check that tylode is connected and see its tools.

#Claude Desktop

The easiest way is to add Tylode as a connector, with no token (see above). If you'd rather use a personal token, connect Claude Desktop through mcp-remote. You need Node.js installed.

1. In Claude Desktop, open Settings → Developer → Edit Config. This opens claude_desktop_config.json (on macOS in ~/Library/Application Support/Claude/, on Windows in %APPDATA%\Claude\).
2. Add Tylode under mcpServers:

{
  "mcpServers": {
    "tylode": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.tylode.com/api/mcp",
        "--header",
        "Authorization:${TYLODE_AUTH_HEADER}"
      ],
      "env": {
        "TYLODE_AUTH_HEADER": "Bearer tylode_pat_xxx"
      }
    }
  }
}

3. Quit Claude Desktop completely and open it again. Tylode's tools appear in the tools menu of the chat box.

Writing Authorization:${TYLODE_AUTH_HEADER} without a space, with the whole Bearer … value in the variable, avoids a problem some clients have on Windows with spaces inside arguments.

#Cursor

Add Tylode to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "tylode": {
      "url": "https://app.tylode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TYLODE_TOKEN}"
      }
    }
  }
}

Set TYLODE_TOKEN in your shell profile or system environment and restart Cursor. Check the connection in the MCP section of Cursor's settings. If you'd rather not use a variable, write the token directly, but then don't commit the file.

#VS Code

Create .vscode/mcp.json in your project (or run MCP: Open User Configuration for all projects). VS Code asks for the token the first time and stores it securely:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "tylode-token",
      "description": "Tylode personal access token",
      "password": true
    }
  ],
  "servers": {
    "tylode": {
      "type": "http",
      "url": "https://app.tylode.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:tylode-token}"
      }
    }
  }
}

Start the server from the file (VS Code shows a Start action above it) and use the tools from Copilot Chat in agent mode.

#Other MCP clients

Any client that supports Streamable HTTP and custom headers works with the URL and header from the table above. The equivalent JSON in most clients is:

{
  "mcpServers": {
    "tylode": {
      "url": "https://app.tylode.com/api/mcp",
      "headers": { "Authorization": "Bearer tylode_pat_xxx" }
    }
  }
}

For clients that only support stdio, run the bridge as the server command:

TYLODE_TOKEN=tylode_pat_xxx npx -y mcp-remote https://app.tylode.com/api/mcp --header "Authorization: Bearer ${TYLODE_TOKEN}"

To test the server by hand, call a tool with curl. The Accept header must list both JSON and event streams:

curl https://app.tylode.com/api/mcp \
  -H "Authorization: Bearer tylode_pat_xxx" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_workspaces","arguments":{}}}'

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "[{\"id\":\"7c1e2a4b-3f5d-4e8a-9b21-6d0f5c8e1a37\",\"name\":\"Acme\",\"slug\":\"acme\",\"plan\":\"pro\",\"role\":\"owner\",\"frozen\":false}]"
      }
    ]
  },
  "jsonrpc": "2.0",
  "id": 1
}

Use "method":"tools/list" to get every tool with its input schema.

#Tools

Every tool returns the API's data as JSON text. When the API refuses a call, the tool returns an error result with the status code and message (for example Error 404: …), and the assistant usually explains it to you.

Parameters with ? are optional. The details of each call are in the API reference: pages, databases, boards, calendar, chats, mail and notifications, and whiteboards, presentations, search and My drive.

With a connector, the delete tools (delete_…) only appear if you authorize their :delete permission, which is unticked on the authorization screen; with a personal token, the assistant sees all of them. Anything with a trash in the app (pages, boards, whiteboards, presentations and My drive files) goes to the trash and can be recovered; cards, events, rows, slides and elements are deleted for good. See Deleting: trash or permanent.

#Example prompts

• "List my Tylode workspaces and tell me which ones are on Pro."
• "Search Acme for 'Q4 budget' and summarize what the page says."
• "What's on my calendar next week? Group it by day."
• "Create a card called 'Prepare the demo' on the Launch board, in the 'Doing' list, with a checklist of steps in the description."
• "Read the last 30 messages in the Product team chat and draft a reply to the question about the release date. Show it to me before sending."
• "Move the 'Prepare the demo' card to the 'Done' list and set its due date to Friday."
• "Add an expense of 12.40 in Food with today's date to the Transactions table."
• "Create a page called 'Retro 23 September' with sections for what went well, what didn't and actions."
• "Do I have unread notifications? Tell me which ones need an answer, then mark them as read."
• "Find the PDF of the signed contract in My drive and give me the download link."

#Rate limits

The MCP server shares the API limit of 60 requests per minute per user. Each tool call counts as 1 request (the API call it makes), except list_cards, which counts as 2 (it reads the lists and the cards), so an assistant can make about 60 tool calls a minute. Connecting and listing tools don't use those 60: they have their own, generous limit (120 a minute). Other scripts using your tokens in the same minute take from the same 60. See Rate limits.

#Security

• The token has full access to your account. Through it, an assistant can read everything you can and write in your name: create pages, change cards and rows, upload files to My drive, send chat messages and mail.
• Keep the token private. Prefer environment variables or the client's secure input, and don't commit configuration files that contain it.
• Review what the assistant does. Most clients ask for approval before each tool call; keep that on for tools that write or send.
• With a connector, grant only what you need. The assistant doesn't see the tools for permissions you don't give it. Leave the delete permissions unticked if it doesn't need them.
• With a personal token, the assistant can delete too. It sees every tool, the delete ones included. If your client asks for approval before each call, keep that on for the delete_… tools.
• Use a dedicated token for each assistant. If it leaks, or you stop using the assistant, revoke it in Settings → API and webhooks → API and plugins and nothing else breaks.
• See what it has done. On that same screen, What your apps and tokens have done lists everything a connected app or a token has created, changed or deleted on your behalf (for example, "Claude · Deleted a card"), for 90 days.
• Be careful with content you didn't write. A page or message from someone else could contain instructions aimed at the assistant. Check before approving actions the assistant proposes after reading it.

#Troubleshooting

#Related pages

• Authentication: create and revoke tokens.
• AI assistant: Tylode's built-in assistant, no setup needed.
• Developer platform: the REST API behind every tool.