Connect your assistant to Otis. Paste one URL, sign in with your email, then just ask.
https://mcp.otisbase.com/mcpSteps for your assistant
Claude
Claude on the web, the desktop app and Cowork · remote custom connector
Open Customize → Connectors and add a custom connector named Otisbase.
Enter the server URL below. Select OAuth sign-in and automatic client registration when offered.
https://mcp.otisbase.com/mcpVerify your email in the Otisbase browser window and authorize access.
Enable the connector in your conversation’s connector menu.
A workspace owner may need to add the connector first. The connector follows your Claude account into the desktop app and Cowork.
ChatGPT
ChatGPT on the web · custom MCP plugin
Open ChatGPT’s Plugins page. Use the plus button and choose Add custom MCP server.
Name it Otisbase, paste the server URL below and choose OAuth. Use dynamic client registration (DCR) if asked for a registration method.
https://mcp.otisbase.com/mcpComplete the browser sign-in when prompted, review the connection information and create the plugin.
Install the resulting personal or workspace plugin. In a chat, type @ and select Otisbase before your first request.
Custom MCP access depends on your workspace permissions and security settings. This creates a custom connection; Otisbase is not a published directory plugin.
Muse
Meta’s Muse · custom connector requested in chat
Start a Muse conversation and ask it to create a custom connector using the setup message below.
Create a custom connector named Otisbase for the remote MCP server at https://mcp.otisbase.com/mcp. It uses Streamable HTTP and OAuth with dynamic client registration. Help me complete the browser sign-in, then check that you can retrieve my business profile. If this authentication flow is not supported, tell me where it stops.Review the connector Muse proposes. Complete Otisbase email verification in the browser authorization flow if Muse can start it.
Ask Muse to retrieve your business profile before trying a write. An empty profile is a valid result for a new account.
The custom-connector route is documented. Muse’s complete OAuth connection to Otisbase still needs a client test; these instructions do not claim a verified integration or directory listing.
Meta: how Muse works with connectors Muse connector platform
Grok Bot
SpaceX’s Grok Bot · custom MCP connection requested in chat
Open a Grok Bot conversation. Custom MCP connections are added by asking your bot, rather than through the app directory.
Add Otisbase as a custom MCP server: https://mcp.otisbase.com/mcp. It uses Streamable HTTP and OAuth with dynamic client registration. Start the authorization flow so I can sign in, then check the connection by retrieving my business profile.Confirm the connection details the bot presents. Follow its Authenticate or Authorize action and finish Otisbase sign-in in the browser.
Send your first business request in the next message, after the tools become available.
Otisbase’s OAuth callback flow has not yet been tested in Grok Bot. A connector appearing in the list is not proof that sign-in and tool calls succeeded.
Cursor support: custom Grok Bot connectors SpaceX: Grok Bot apps and authentication
Mistral Vibe
Mistral Vibe, formerly Le Chat · custom MCP connector
Open Connectors, choose + Add Connector, then the Custom MCP Connector tab.
Name it otis and paste the server URL below. Choose Connect: Vibe detects OAuth sign-in by itself.
https://mcp.otisbase.com/mcpComplete Otisbase sign-in in the browser window that opens.
In a conversation, turn on the otis connector and ask for the Otis menu.
Adding a connector is an admin task. On Free and Pro plans the account owner is the admin; on Team plans, ask your admin.
Claude Code
Terminal or editor agent · remote HTTP server
Add Otis to Claude Code using the HTTP transport:
claude mcp add --transport http otis https://mcp.otisbase.com/mcpOpen Claude Code and enter /mcp. Select Otis and start its authentication flow.
Complete Otisbase email verification in the browser. Return to Claude Code and check that the server is connected before making your first request.
Codex
CLI · configuration shared with local Codex clients
With the Codex CLI installed, add the hosted server and start OAuth login:
codex mcp add otis --url https://mcp.otisbase.com/mcp codex mcp login otisVerify your email and authorize Otisbase in the browser window.
Run codex mcp list to inspect the configured server. Start a Codex conversation; /mcp in the CLI shows active servers.
In the IDE extension, you can instead open the gear menu → MCP servers → Add server, choose Streamable HTTP, save, restart the extension and select Authenticate.
Cursor
Cursor Agent · remote MCP in mcp.json
Add this entry to your existing .cursor/mcp.json, or use ~/.cursor/mcp.json for your user configuration. Preserve any other servers already in the file.
.cursor/mcp.json{ "mcpServers": { "otis": { "url": "https://mcp.otisbase.com/mcp" } } }Open Cursor’s MCP settings and authenticate Otis when prompted. Finish email verification and authorization in your browser.
Use Agent chat with the Otis tools enabled, then send your first request.
Any other MCP client
Any client that supports remote MCP servers with OAuth sign-in
In your client’s MCP settings, add a remote server using Streamable HTTP and this URL:
https://mcp.otisbase.com/mcpIf your client is set up with a JSON file, this entry works in most of them:
{ "mcpServers": { "otis": { "url": "https://mcp.otisbase.com/mcp" } } }Choose OAuth sign-in. If your client asks how to register, choose dynamic client registration.
Sign in with the code we email you, in the browser window that opens.
Ask your assistant for the Otis menu to check the connection.
Otis runs only as a remote server. Clients that can run only local MCP servers can’t connect.
After you connect. Try these in your first minute with Otis.
Open the menu. See every task Otis can help with, and pick one by number.
Show me the Otis menu.Set up your business. Otis asks for your details, invoice numbering and tax profile.
Set up my business with Otis.
Questions
Is there an app or a dashboard?
No. Otis is MCP-only: there is no app, dashboard or client portal. You work in your AI assistant, and it calls Otis’s tools over MCP.
What is MCP?
The Model Context Protocol is an open standard that lets AI assistants use outside tools. Otis is an MCP server: your assistant connects to one URL and gets Otis’s tools.
Which assistants work with Otis?
Any MCP client that supports remote servers over Streamable HTTP with OAuth sign-in. The guides above cover the eight most used, and the general steps cover the rest.
Do I need an API key or a password?
No. The first time you connect, you sign in with your email and a code in the browser. That creates your free account.
Can I connect more than one assistant?
Yes. Sign in with the same email in each one, and they all work with the same records.
Can my team use it?
Yes. An owner invites people by email as editors or viewers, and each person connects their own assistant.
How do I suggest a feature?
Ask your assistant to send feedback to Otis. It shows you the message first and sends it only when you approve.
Is it free?
Yes. This version of Otisbase is free and stays free. Your AI assistant’s subscription remains separate. Pricing and fair use
Who runs Otis?
Otis is built and run by Boon IT SRL, a small software company in Cluj-Napoca, Romania. Business records are stored in the European Union. About Otis
Does Otis read my conversations?
No. Your assistant calls Otis to save or read specific records. Otis stores those records, not your chat history.
Where are my records, and can I get them out?
Each business has its own database on Cloudflare, stored in the European Union. Ask for an export at any time, and your assistant can turn it into a CSV for your accountant.
Need a hand? We’re here to help, whether you’re connecting your assistant or have a question about your records.
Email support