Smitline
Sign in
Docs menu

Docs Connect

Connect your agent

Smitline is an MCP server. Most agents connect to it with one address and your Smitline sign-in, with no API key to copy:

https://app.smitline.com/mcp

Agents that can't sign in can send an API key instead: make one in the dashboard under Connect → API keys and use it as Authorization: Bearer YOUR_SMITLINE_KEY. Programs that don't speak MCP use the REST API.

Agent menus change often. These steps were checked against each maker's own documentation. If a step doesn't match what you see, follow the maker's link under the agent.

Chat apps

Add Smitline as a connector and sign in. No code.

ChatGPT

You need: ChatGPT on the web, on any plan, Free included. On a Business, Enterprise or Edu workspace, an admin has to allow it first.

  1. In ChatGPT on the web, open Plugins, click + and choose Add custom MCP server.
  2. Name it Smitline, paste the server URL, and set authentication to OAuth:
https://app.smitline.com/mcp
  1. Tick I understand and want to continue, choose Create as a plugin, check the tools, and install it.
  2. Sign in to Smitline when asked, and allow access. Then, in a new chat, type @ and pick Smitline.
  • On ChatGPT Business, only admins and owners can add a custom MCP server. On Enterprise and Edu, an admin grants the “Create plugins with MCPs” permission.
  • ChatGPT asks you to confirm before Smitline places a call. That’s expected; keep it on.
  • Custom MCP servers work on the ChatGPT website only, not in the mobile apps.

More in OpenAI: add a custom MCP server (opens in a new tab), OpenAI: plugins in ChatGPT (opens in a new tab).

Claude

You need: Any Claude plan (Free allows one custom connector), on the web or desktop.

  1. In Claude, open Customize → Connectors, click + Add and choose Add custom connector.
  2. Name it Smitline, paste the URL and click Continue:
https://app.smitline.com/mcp
  1. Choose Sign in now and click Add. Sign in to Smitline and allow access. If Claude asks which OAuth client to use, Register automatically works.
  2. In a chat, click + → Connectors and turn Smitline on, then ask for a call.
  • Claude asks before each tool call. Don’t choose “Allow always” for placing calls: each one costs money.
  • On Team and Enterprise, an owner adds Smitline once under Organization settings → Connectors; each member then clicks Connect and signs in with their own Smitline account.
  • A connector you add on the web or desktop also works in the Claude mobile apps.

More in Claude: custom connectors (opens in a new tab).

Grok

You need: Grok at grok.com. On Grok Business or Enterprise, an admin adds the connector first.

  1. Go to grok.com/connectors, click New Connector and choose Custom.
  2. Paste the MCP server URL:
https://app.smitline.com/mcp
  1. Sign in to Smitline when Grok asks, and allow access. Grok then uses Smitline when you ask for a call.
  • Grok Business and Enterprise: an admin adds it in console.x.ai → Grok Business → Connectors → Add Connector → Other, then members connect at grok.com/connectors.
  • If Grok offers a request header instead of sign-in, use Authorization with the value Bearer YOUR_SMITLINE_KEY.
  • Connectors are documented for grok.com; Grok in the X app may not have them yet.

More in xAI: Grok connectors (opens in a new tab).

Meta Muse

You need: Muse in the US or Canada, in the app or on the web. A Smitline API key.

  1. In your Smitline dashboard, open Connect → API keys and click Create key. Keep the page open: the key is shown once.
  2. In Muse, send this message:
Set up Smitline as a custom connector: https://smitline.com/agents
  1. Muse reads the setup page and asks for your key. Paste it into Muse’s Secure Credentials prompt, never into the chat.
  2. Approve the connector, then try it: “Use Smitline to call my phone for a quick test.”
  • In Settings → Permissions, keep Muse asking before actions, so you approve each call before it’s placed.
  • Muse connects to Smitline’s REST API, not MCP: Muse’s own help says custom connectors use a service’s API.
  • Muse checks on a call every few seconds, so its answers during a call come a little slower than in other apps.

More in Muse Help Center: connectors (opens in a new tab).

Mistral Vibe

You need: Vibe (formerly Le Chat) at chat.mistral.ai. On team plans, an admin adds connectors.

  1. In Vibe, open Connectors in the sidebar, click + Add Connector and open the Custom MCP Connector tab.
  2. Name it smitline (no spaces) and paste the server URL:
https://app.smitline.com/mcp
  1. Click Connect, sign in to Smitline and allow access. Or choose Bearer token and paste your API key.
  2. In a chat, open + → Tools and turn Smitline on.
  • Le Chat became Vibe on 12 August 2026; connectors live in its Work mode.
  • Leave Smitline’s call tool on manual approval rather than “Always allow”.

More in Mistral: MCP connectors (opens in a new tab).

Perplexity

You need: Perplexity Pro, Max or Enterprise.

  1. Open Plugins in the sidebar (or Customize → Connectors), then Add custom → Add MCP connector → Remote.
  2. Name it Smitline and paste the server URL:
https://app.smitline.com/mcp
  1. Under Advanced, set authentication to OAuth and transport to Streamable HTTP. Tick the acknowledgement and click Add.
  2. Click the Smitline card to sign in and turn it on. Then ask: “Using Smitline, call …”.
  • On Enterprise, admins add custom connectors in Organization settings → Connectors, or allow members to add their own.

More in Perplexity: custom remote connectors (opens in a new tab).

Coding agents and editors

One command or a few lines of config.

Claude Code

You need: Claude Code in the terminal, the desktop app or an IDE.

  1. Add Smitline from a terminal. --scope user makes it available in every project:
claude mcp add --transport http --scope user smitline https://app.smitline.com/mcp
  1. In Claude Code, run /mcp, choose smitline and Authenticate. Sign in to Smitline and allow access.

Or use an API key:

  1. Add Smitline with your key in a header instead of signing in:
claude mcp add --transport http --scope user smitline https://app.smitline.com/mcp \
  --header "Authorization: Bearer YOUR_SMITLINE_KEY"
  • Headless runs (claude -p) can’t open a browser to sign in. Sign in once from an interactive session, or use an API key.
  • For a team, --scope project writes .mcp.json into the repository; each person approves it once.

More in Claude Code: MCP (opens in a new tab).

Codex

You need: Codex CLI, the Codex IDE extension or the ChatGPT desktop app.

  1. Add Smitline from a terminal. Codex finds the sign-in and opens your browser:
codex mcp add smitline --url https://app.smitline.com/mcp
  1. Sign in to Smitline and allow access. To sign in again later, run codex mcp login smitline.
  2. In the ChatGPT desktop app or the IDE extension instead: open Settings → MCP servers → Add server, choose Streamable HTTP, paste the URL, save, restart, then Authenticate.

Or use an API key:

  1. Add this to ~/.codex/config.toml:
~/.codex/config.toml
[mcp_servers.smitline]
url = "https://app.smitline.com/mcp"
bearer_token_env_var = "SMITLINE_API_KEY"
  1. Set the key in your shell profile, then restart Codex:
export SMITLINE_API_KEY=YOUR_SMITLINE_KEY
  • The CLI, the IDE extension and the ChatGPT desktop app share ~/.codex/config.toml, so adding Smitline once covers all three.
  • Run /mcp in Codex to check that Smitline is connected.

More in Codex: MCP (opens in a new tab).

Cursor

You need: Cursor on any plan.

  1. Add Smitline to ~/.cursor/mcp.json (or .cursor/mcp.json in one project):
~/.cursor/mcp.json
{
  "mcpServers": {
    "smitline": {
      "url": "https://app.smitline.com/mcp"
    }
  }
}
  1. Cursor shows Smitline under Customize → MCP. Click Connect, sign in to Smitline and allow access.

Or use an API key:

  1. Add a header with your key instead:
~/.cursor/mcp.json
{
  "mcpServers": {
    "smitline": {
      "url": "https://app.smitline.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" }
    }
  }
}
  • Cursor asks before it uses a tool. Approve Smitline’s call tool when the agent asks.
  • If it doesn’t connect, open Output → MCP Logs.

More in Cursor: MCP (opens in a new tab).

Gemini CLI

You need: Gemini CLI, any recent version.

  1. Add Smitline for your user (not just this folder):
gemini mcp add --transport http -s user smitline https://app.smitline.com/mcp
  1. Start Gemini CLI and run /mcp auth smitline. Sign in to Smitline and allow access.

Or use an API key:

  1. Add Smitline with your key in a header:
gemini mcp add --transport http -s user \
  --header "Authorization: Bearer YOUR_SMITLINE_KEY" smitline https://app.smitline.com/mcp
  • Gemini CLI asks you to confirm each tool call unless you trust the server.
  • Editing ~/.gemini/settings.json by hand? Use httpUrl, not url: url means the older SSE transport.

More in Gemini CLI: MCP servers (opens in a new tab).

Devin Desktop

You need: Devin Desktop (formerly Windsurf) or Devin CLI.

  1. Add Smitline with Devin CLI:
devin mcp add -s user smitline https://app.smitline.com/mcp
  1. Sign in to Smitline and allow access:
devin mcp login smitline
  1. In Devin Desktop, Smitline then shows under Customize → MCPs. If it says Needs auth, click Authenticate.

Or use an API key:

  1. Add Smitline to mcp_config.json with a header (%APPDATA%\devin\mcp_config.json on Windows):
~/.config/devin/mcp_config.json
{
  "mcpServers": {
    "smitline": {
      "url": "https://app.smitline.com/mcp",
      "transport": "http",
      "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" }
    }
  }
}
  • Windsurf became Devin Desktop on 2 June 2026. An old Windsurf mcp_config.json is still read.
  • MCP tools ask for approval by default. On Teams and Enterprise, an admin may need to allow Smitline.

More in Devin: MCP configuration (opens in a new tab).

VS Code

You need: VS Code 1.99 or later with GitHub Copilot. On Copilot Business or Enterprise, an admin turns on MCP.

  1. Add Smitline from a terminal:
code --add-mcp '{"name":"smitline","type":"http","url":"https://app.smitline.com/mcp"}'
  1. Or in VS Code: Command Palette → MCP: Add Server → HTTP, paste the URL and name it smitline.
  2. Start the server when VS Code asks, sign in to Smitline and allow access. Then use Copilot Chat in Agent mode.

Or use an API key:

  1. In mcp.json, ask for the key once and send it as a header:
mcp.json
{
  "inputs": [
    { "type": "promptString", "id": "smitline-key", "description": "Smitline API key", "password": true }
  ],
  "servers": {
    "smitline": {
      "type": "http",
      "url": "https://app.smitline.com/mcp",
      "headers": { "Authorization": "Bearer ${input:smitline-key}" }
    }
  }
}
  • Copilot Business and Enterprise: the “MCP servers in Copilot” policy is off by default. Ask your admin.
  • VS Code asks you to trust the server and approve tool calls. Approve Smitline’s call tool when Copilot asks.

More in VS Code: MCP servers (opens in a new tab), GitHub Copilot: MCP (opens in a new tab).

Junie

You need: Junie in a JetBrains IDE or the Junie CLI, with a JetBrains AI licence.

  1. Add Smitline to ~/.junie/mcp/mcp.json (in the IDE: Settings → Tools → Junie → MCP Settings → Add opens the same file):
~/.junie/mcp/mcp.json
{
  "mcpServers": {
    "smitline": {
      "url": "https://app.smitline.com/mcp"
    }
  }
}
  1. Junie shows Authorization required. Run /mcp, choose Authorize, sign in to Smitline and allow access.

Or use an API key:

  1. Add a header instead:
~/.junie/mcp/mcp.json
{
  "mcpServers": {
    "smitline": {
      "url": "https://app.smitline.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" }
    }
  }
}
  • JetBrains AI Assistant’s own chat can’t sign in to remote MCP servers yet; use Junie.

More in Junie: MCP configuration (opens in a new tab).

Zed

You need: Zed, any recent version.

  1. Open Settings → AI → MCP Servers → Add Server → Add Remote Server, or add this to your settings file (zed: open settings file):
settings.json
"context_servers": {
  "smitline": {
    "url": "https://app.smitline.com/mcp"
  }
}
  1. Zed asks you to sign in. Sign in to Smitline and allow access. A green dot means it’s connected.

Or use an API key:

  1. Add a header to the same entry. Zed then skips the sign-in:
settings.json
"context_servers": {
  "smitline": {
    "url": "https://app.smitline.com/mcp",
    "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" }
  }
}
  • Zed asks before running tools by default. Keep it that way for Smitline: each call costs money.

More in Zed: MCP (opens in a new tab).

Cline

You need: Cline in VS Code, or the Cline CLI.

  1. In the Cline panel, click the MCP Servers icon, then Configure → Remote Servers.
  2. Server name smitline, transport Streamable HTTP, and the URL:
https://app.smitline.com/mcp
  1. Click Add Server, then Authenticate, sign in to Smitline and allow access. Start a new chat afterwards.

Or use an API key:

  1. In cline_mcp_settings.json (Configure MCP Servers), set the type and a header:
cline_mcp_settings.json
{
  "mcpServers": {
    "smitline": {
      "type": "streamableHttp",
      "url": "https://app.smitline.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" },
      "disabled": false,
      "autoApprove": []
    }
  }
}
  • Always set "type": "streamableHttp": without it Cline uses the older SSE transport.
  • Signing in needs a browser on the same machine; over remote desktop, use an API key.

More in Cline: remote MCP servers (opens in a new tab).

goose

You need: goose Desktop or CLI (originally from Block).

  1. In goose Desktop: Extensions → Add custom extension, type Remote Extension (Streamable HTTP), and the endpoint:
https://app.smitline.com/mcp
  1. Click Add. goose opens your browser: sign in to Smitline and allow access.
  2. In the CLI instead: run goose configure → Add Extension → Remote Extension (Streamable HTTP), name it smitline and paste the URL.

Or use an API key:

  1. Add a custom request header when goose asks (or in config.yaml):
~/.config/goose/config.yaml
extensions:
  smitline:
    type: streamable_http
    name: smitline
    enabled: true
    uri: https://app.smitline.com/mcp
    headers:
      Authorization: "Bearer YOUR_SMITLINE_KEY"
    timeout: 300
  • goose runs tools without asking by default. Set GOOSE_MODE to approve or smart_approve so you confirm each call.

More in goose: extensions (opens in a new tab).

OpenCode

You need: OpenCode, any recent version.

  1. Add Smitline to ~/.config/opencode/opencode.json:
~/.config/opencode/opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smitline": {
      "type": "remote",
      "url": "https://app.smitline.com/mcp",
      "enabled": true
    }
  }
}
  1. Sign in to Smitline and allow access:
opencode mcp auth smitline

Or use an API key:

  1. Use a header, and turn off sign-in so OpenCode doesn’t try it:
~/.config/opencode/opencode.json
"smitline": {
  "type": "remote",
  "url": "https://app.smitline.com/mcp",
  "enabled": true,
  "oauth": false,
  "headers": { "Authorization": "Bearer {env:SMITLINE_API_KEY}" }
}
  • opencode mcp list shows whether Smitline is connected; opencode mcp debug smitline helps when it isn’t.

More in OpenCode: MCP servers (opens in a new tab).

Warp

You need: Warp with agents turned on.

  1. In Warp, open Settings → Agents → MCP servers and click + Add.
  2. Paste this and save. Warp opens your browser to sign in to Smitline:
{
  "smitline": {
    "url": "https://app.smitline.com/mcp"
  }
}

Or use an API key:

  1. Paste this instead:
{
  "smitline": {
    "url": "https://app.smitline.com/mcp",
    "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" }
  }
}
  • Warp’s cloud agents need the API key version: they can’t complete a browser sign-in.

More in Warp: MCP (opens in a new tab).

Personal agents and automation

Agents that run for you, and workflow tools.

OpenClaw

You need: OpenClaw with its Gateway.

  1. Add Smitline. Always set the transport; OpenClaw assumes the older SSE without it:
openclaw mcp add smitline --url https://app.smitline.com/mcp \
  --transport streamable-http --auth oauth
  1. Stop the Gateway, sign in to Smitline, then start the Gateway again:
openclaw gateway stop
openclaw mcp login smitline

Or use an API key:

  1. Set Smitline with a header that reads your key from SMITLINE_API_KEY, then check it:
openclaw mcp set smitline '{"url":"https://app.smitline.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${SMITLINE_API_KEY}"}}'
openclaw mcp doctor smitline --probe
  • Prefer ${SMITLINE_API_KEY} over pasting the key into the config: openclaw mcp doctor warns about keys in plain text.

More in OpenClaw: MCP (opens in a new tab).

Hermes Agent

You need: Hermes Agent, any recent version.

  1. Add Smitline to ~/.hermes/config.yaml:
~/.hermes/config.yaml
mcp_servers:
  smitline:
    url: "https://app.smitline.com/mcp"
    auth: oauth
  1. Sign in to Smitline (on a machine without a browser, add --flow device):
hermes mcp login smitline
  1. Check it, then run /reload-mcp in a running session:
hermes mcp test smitline

Or use an API key:

  1. Use a header instead of auth: oauth:
~/.hermes/config.yaml
mcp_servers:
  smitline:
    url: "https://app.smitline.com/mcp"
    headers:
      Authorization: "Bearer YOUR_SMITLINE_KEY"
  • If your browser refuses the sign-in redirect to 127.0.0.1, set oauth.redirect_host: localhost for the server.

More in Hermes Agent: MCP (opens in a new tab).

n8n

You need: n8n Cloud or self-hosted, with the AI Agent node.

  1. On your AI Agent node, add a tool and choose MCP Client Tool.
  2. Set Endpoint to the MCP server URL and Server Transport to HTTP Streamable:
https://app.smitline.com/mcp
  1. Set Authentication to MCP OAuth2 and connect, or to Bearer Auth with a credential whose token is your Smitline API key.
  2. Under Tools to Include, pick All, or only the ones the workflow needs.
  • For a fixed workflow without an AI agent, an HTTP Request node can start a call with POST https://app.smitline.com/v1/calls and your key.
  • With OAuth, n8n registers its own redirect URL; nothing to copy into Smitline.

More in n8n: MCP Client Tool (opens in a new tab).

LibreChat

You need: LibreChat, self-hosted.

  1. Add Smitline to librechat.yaml. Each user then signs in with their own Smitline account:
librechat.yaml
mcpServers:
  smitline:
    type: streamable-http
    url: https://app.smitline.com/mcp
  1. Restart LibreChat. Users pick smitline in a chat and sign in when asked.

Or let each user paste their own API key:

  1. Ask each user for their key instead of a sign-in:
librechat.yaml
mcpServers:
  smitline:
    type: streamable-http
    url: https://app.smitline.com/mcp
    requiresOAuth: false
    headers:
      Authorization: "Bearer {{SMITLINE_API_KEY}}"
    customUserVars:
      SMITLINE_API_KEY:
        title: "Smitline API key"
        sensitive: true
  • Don’t put one shared key in an environment variable: every user would call from the same Smitline account and wallet.

More in LibreChat: MCP servers (opens in a new tab).

Raycast

You need: Raycast Pro, on Mac or iOS.

  1. Run Install MCP Server in Raycast.
  2. Name it smitline, set Transport to HTTP, and paste the URL:
https://app.smitline.com/mcp
  1. Set OAuth Type to Dynamic, press Install, then Sign In to Smitline.
  2. In AI Chat, mention @smitline and ask for a call.

Or use an API key:

  1. Instead of OAuth, add an HTTP header: Authorization with the value Bearer YOUR_SMITLINE_KEY.
  • MCP in Raycast needs a Pro plan.

More in Raycast: Model Context Protocol (opens in a new tab).

Build your own

Call Smitline from your own code, through MCP or the REST API.

Claude API

You need: An Anthropic API key and a Smitline API key.

  1. Pass Smitline in mcp_servers and turn its tools on with an mcp_toolset:
curl https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "anthropic-beta: mcp-client-2026-09-15" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-opus-5-5",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Call +1 416 555 0134 and ask if they have a table for 2 at 7pm."}],
    "mcp_servers": [{"type": "url", "url": "https://app.smitline.com/mcp", "name": "smitline", "authorization_token": "YOUR_SMITLINE_KEY"}],
    "tools": [{"type": "mcp_toolset", "mcp_server_name": "smitline"}]
  }'
  • The MCP connector is in beta. On Claude Platform on AWS, Google Cloud or Microsoft Foundry, use the beta header mcp-client-2025-11-20.
  • A call takes minutes. Start it, then check back with Smitline’s wait_for_call tool in a later turn.

More in Claude: MCP connector (opens in a new tab).

OpenAI API

You need: An OpenAI API key and a Smitline API key.

  1. Add Smitline as an mcp tool in a Responses API request:
POST https://api.openai.com/v1/responses
{
  "model": "gpt-6-astra",
  "input": "Call +1 416 555 0134 and ask if they are open on Sunday.",
  "tools": [{
    "type": "mcp",
    "server_label": "smitline",
    "server_url": "https://app.smitline.com/mcp",
    "headers": { "Authorization": "Bearer YOUR_SMITLINE_KEY" },
    "require_approval": "always"
  }]
}
  1. With require_approval on, answer each mcp_approval_request with an mcp_approval_response. In the Agents SDK, use HostedMCPTool with the same settings, or MCPServerStreamableHttp.
  • Send the headers with every request.

More in OpenAI: MCP and connectors (opens in a new tab), Agents SDK: MCP (opens in a new tab).