Connect a client

The Forktime MCP server is a standard remote MCP endpoint:

https://api.forktime.ai/mcp

Anything that speaks MCP (Streamable HTTP) can use it — your own agent, or an off-the-shelf client. How you authenticate depends on the client: interactive apps use OAuth; servers and CLIs use an API key.

Your own app

Use any MCP client library, point it at the endpoint, and attach your credential — a Bearer gfk_… API key for a backend, or the OAuth flow for an interactive app. Then the standard MCP handshake applies: the server lists its tools, and you call list_brands first to get a slug to pass on every other call.

Off-the-shelf clients

claude.ai / Claude Desktop

These require OAuth — you sign in and approve in the browser.

1. Open Settings → Connectors → Add custom connector.
2. Paste https://api.forktime.ai/mcp.
3. Click Connect and approve the Forktime sign-in.
4. Ask it to list_brands to confirm.

Cursor

1. Open Settings → MCP → Add new MCP server.
2. Add an HTTP server at https://api.forktime.ai/mcp.
3. Approve the OAuth flow on first use.

Claude Code

Claude Code supports a static token, so use an API key:

claude mcp add --transport http forktime https://api.forktime.ai/mcp \
  --header "Authorization: Bearer gfk_live_your_key_here"

Verify

Whatever the client, the first successful call should be list_brands. If it returns your brands, you’re connected. A 401 means the credential wasn’t accepted; a “not permitted” tool error means it’s valid but missing that scope.