Connect Botable
to your AI agents

Your agent describes the bot. Botable writes it, gives it a database, puts it online and keeps it running. No servers, no deploys, nothing to maintain.

Works where you already work

Claude CodeClaudeCursorCodexZedClineOpenCodeWindsurfContinueVS CodeHermes AgentOpenClaw

You never leave the conversation you were already in. And it is the same Botable underneath: bots built this way show up in your account exactly as they would if you had made them on the site, so you can carry on with them in either place.

How to connect it

Pick your assistant below. The first time you use it, a browser window opens and asks you to sign in to Botable, that is how it knows which bots are yours. There is no API key to generate and nothing to paste back.

Claude Code

One command in your terminal.

Terminal
claude mcp add --transport http botable https://mcp.botable.io/mcp

Claude desktop & web

Settings → Connectors → Add custom connector, then paste the URL.

Server URL
https://mcp.botable.io/mcp

Cursor

Add this to your MCP config and restart Cursor.

~/.cursor/mcp.json
{  "mcpServers": {    "botable": { "url": "https://mcp.botable.io/mcp" }  }}

Using something else? Any assistant that supports remote MCP servers will work, point it at https://mcp.botable.io/mcp and it will handle the sign-in itself.

What you can ask for

Once it is connected, these are the kinds of things to say.

Build a new bot

Describe the bot you want and it gets built, given its own database, and put online, without you leaving the conversation. If you do not have a bot token yet, it hands you a link to tap in Telegram and takes care of the rest.

“Build me a Telegram bot that tracks Bitcoin and alerts me when it moves 5%.”

Change a bot you already have

Ask for the change in plain language. The bot is updated and reloaded in place, so it keeps its users and everything it has already stored.

“Add a /stats command to my reminder bot.”

Check how a bot is doing

See which of your bots are awake, what a bot has been doing, and what it logged when something went wrong, useful when a bot has gone quiet and you want to know why.

“Is my support bot running, and has it thrown any errors today?”

Start, stop and tidy up

Turn a bot on or off, swap in a new token if you regenerated one, or delete a bot you are finished with.

“Stop the quiz bot for now, I am done testing it.”

Worth knowing

It only ever touches your own bots. Signing in is what links the connector to your account, and every action is checked against it.

Your bot's code stays yours. The connector can build and change a bot, and tell you what it did, but it will not hand the source code of your bot to an assistant.

Building costs credits, running does not. Exactly the same as on the site, a credit is spent when a bot is built or changed, and a finished bot keeps serving people for free. See pricing.

Building takes a few minutes. Your assistant will wait and tell you when the bot is live, so you can go and do something else in the meantime.

No Botable account yet?

You will need one to connect, signing up is free and comes with enough credits to build your first bot.

Get started