https://platform.jobbit.uk/mcp (streamable HTTP). An agent connected to it can run Jobbit agent tasks, call models, deploy and manage apps, work with files, automations, projects and domains, and read your balance. Its tools call the same API as the REST routes, with the same permissions, limits and spend.
The server introduces itself to the agent and points it to a short guide at /skill.md, so the agent knows how to use Jobbit without extra prompting.
Sign in
There are two ways to let an agent in:- OAuth. The client signs in by itself: it opens Jobbit’s consent page, you approve it and choose its permissions. Nothing to copy. Most desktop and web clients work this way.
- An API key. You create a key and give it to the client as a bearer token. Good for command-line tools and servers.
Claude
- claude.ai and Claude Desktop
- Claude Code
- Open Settings → Connectors and choose Add custom connector.
- Name it
Jobbitand enterhttps://platform.jobbit.uk/mcpas the URL. - Choose Connect, then approve the connection on Jobbit’s page.
ChatGPT and Codex
- Codex CLI
- Codex in the IDE
- ChatGPT
Sign in with OAuth:Or use an API key in
~/.codex/config.toml:Any other client
Point any MCP client that supports streamable HTTP athttps://platform.jobbit.uk/mcp. If it supports OAuth, it finds the sign-in from the server’s 401 and registers itself. If not, send an API key in the Authorization: Bearer header.
Manage connections
Every OAuth connection is listed in Settings → Integrations with when it was approved and last used, and appears in your API keys as a key named after the app, such as Claude (OAuth). You can:- Edit that key to narrow what the app may do or cap its spending.
- Disconnect the app in Integrations, or revoke its key. Its next call fails, and it has to sign in again.