Connect an assistant

• Be an owner or admin of the Leitvik workspace you want to connect.
• Use this endpoint: https://app.leitvik.com/api/mcp
• Decide what the assistant may change. Start with read scopes and add writes later.

1. In Claude, add a custom connector with the URL https://app.leitvik.com/api/mcp. Leave the client ID and secret empty.
2. Claude opens Leitvik in your browser. Sign in if asked: authorizing needs a sign-in from the last ten minutes.
3. Choose the workspace and what Claude may do there. Reads are preselected; turn on only the writes it needs.
4. Ask Claude to call leitvik_context and check the workspace name.

1. In ChatGPT, with developer mode on, create a connector with the URL https://app.leitvik.com/api/mcp and OAuth authentication. Leave the client ID and secret empty.
2. ChatGPT opens Leitvik in your browser. Sign in if asked.
3. Choose the workspace and the scopes, then confirm.
4. Ask ChatGPT to call leitvik_context and check the workspace name.

1. Create an API token in Settings > API tokens with the scopes Cursor needs.
2. Set two environment variables where Cursor runs: LEITVIK_URL with https://app.leitvik.com (no trailing slash) and LEITVIK_TOKEN with the token.
3. Merge this server into your .cursor/mcp.json or user MCP configuration, keeping any other servers.
4. Ask the agent to call leitvik_context.

{
  "mcpServers": {
    "leitvik": {
      "url": "${env:LEITVIK_URL}/api/mcp",
      "headers": { "Authorization": "Bearer ${env:LEITVIK_TOKEN}" }
    }
  }
}

Cursor expands ${env:…} from the environment of the running client. A remote server cannot use the stdio-only envFile option.

1. Create an API token in Settings > API tokens. For daily work choose the read scopes plus tasks:write, opportunities:write and captures:write.
2. In a Grok Bot chat, ask: "Add a custom MCP server called leitvik at https://app.leitvik.com/api/mcp".
3. When it asks for authentication, give the header name Authorization and the value Bearer qre_… with your token. Do not paste the token anywhere else in the conversation.
4. Ask Grok to call leitvik_context and confirm the workspace. Keep per-tool approval on for writes until you have seen how it behaves.

Grok Bot runs on a cloud computer, so it needs the public HTTPS endpoint. The header step comes from a third-party walkthrough; we have not found an official xAI page for it.

URL

https://app.leitvik.com/api/mcp

Transport

Streamable HTTP (stateless, JSON responses)

Authentication

OAuth 2.1 with discovery, or the header Authorization: Bearer qre_…

• Check the workspace with leitvik_context before working with CRM data.
• Use one credential per assistant, so you can revoke each on its own.
• To disconnect, revoke the token or the connected application in Settings > API tokens.