How to connect Claude, Cursor and other AI apps with MCP
Every workspace has an MCP server. AI apps such as Claude, Claude Code, Cursor, Codex and Gemini CLI connect to it with a personal key, then read and update your work as you, with your permissions. Why this is useful is on MCP in Worknano. This page is the setup.
Turn it on (admins)
- Open Organization and click Settings. Under MCP Server, switch on Enable MCP Server. It stays off until an admin turns it on.
- Open Config, click Integrations, then MCP Server. Each app (Claude, Cursor, Codex, Gemini) is a connection template. Switch a template off and every key made from it stops working.
- Choose which models each template may read, create or update. Delete is off by default.
- Under Permissions, MCP Permissions sets what external connections may do across the workspace. See Permissions.
- By default, Founders and Heads can connect. To let other roles connect, give them create access to MCP Connection in Permissions.
Connect your app
- Open My and click Integrations. Find Worknano in other AI apps.
- Click Connect beside your app. The row shows the Server URL and your key.
- Copy the Server URL. It is your workspace address with /mcp at the end, for example https://yourcompany.worknano.com/mcp.
- Reveal and copy the key. It starts with wnpat_. Only you can reveal it, and every reveal is recorded.
- Follow the guide on the row for your app. Every app needs the same two things: the Server URL, and an Authorization header whose value is Bearer followed by your key.
Claude Code, in one command:
claude mcp add --transport http --scope user worknano https://yourcompany.worknano.com/mcp --header "Authorization: Bearer YOUR_KEY"
Cursor, in ~/.cursor/mcp.json:
{ "mcpServers": { "worknano": { "url": "https://yourcompany.worknano.com/mcp", "headers": { "Authorization": "Bearer YOUR_KEY" } } } }
Gemini CLI uses httpUrl instead of url. Codex needs Streamable HTTP and the same header. In the Claude app, add a custom connector, choose No sign in and add the header. A connector that an owner adds for a whole Claude team sends one key for everyone, with that key's permissions.
What the app can do
- Read the workspace: models, fields, records, counts and groups.
- Create and update records in the models your template allows.
- List, read and save files (HTML, text and boards).
- Propose config changes as drafts. Nothing changes until an admin approves the draft in Worknano.
Three limits apply to every call: the model's MCP settings, your connection's grants and your own role. Secrets, users, roles and integrations are never exposed.
Keys, expiry and disconnecting
- A key lasts 90 days. When it expires, the row shows Not connected. Click Connect for a new key and paste it into your app.
- Click Disconnect to delete your key. The app loses access at once.
Worknano can also use other MCP servers inside its own assistants. That is the MCP Client, a separate switch next to Enable MCP Server. Calling Worknano from your own code is in the developer docs. Back to the docs map.