Integrations

What it does: Claude Code reads and edits your bases from the terminal: it can design a base, load data, link records, build views or answer questions about your tables.

How to connect: create a personal token in the app (Account › API & tokens) and run:

claude mcp add --transport http openmasu https://platform.openmasu.com/mcp \
  --header "Authorization: Bearer bpat_…"

You can also leave out the header and sign in from /mcp inside Claude Code: OpenMasu supports OAuth with dynamic client registration.

Create a tokenClaude Code MCP docs

What it does: the same 52 tools inside a Claude conversation, on the web or in Claude’s desktop app.

How to connect: in Claude, open Customize › Connectors, press «+ Add» › Add custom connector, name it «OpenMasu» and use the URL https://platform.openmasu.com/mcp. Claude sends you to OpenMasu’s consent screen, where you choose one workspace (or all of them) and allow access. No token to copy. Custom connectors depend on your Claude plan; on Team and Enterprise plans an owner adds the connector first.

You can see and revoke connected apps at any time in Account › Connected apps.

Claude’s guide to custom connectors

What it does: lets ChatGPT read your bases and, if you allow writing, change them.

How to connect: in ChatGPT, open Plugins, press the plus button and choose Add custom MCP server. Enter the URL https://platform.openmasu.com/mcp, choose OAuth authentication and approve access on OpenMasu’s consent screen. Whether you can add custom MCP servers depends on your ChatGPT plan and your workspace’s policies.

OpenAI’s guide to adding an MCP server

What it does: the 52 tools in Codex, from the CLI or the IDE extension.

How to connect: add the server to ~/.codex/config.toml and put your personal token in an environment variable:

[mcp_servers.openmasu]
url = "https://platform.openmasu.com/mcp"
bearer_token_env_var = "OPENMASU_TOKEN"

Without bearer_token_env_var, run codex mcp login openmasu to sign in with OAuth instead.

Create a tokenCodex MCP docs

What it does: Cursor’s agent works on your bases while you code, for example to seed data or check what a table contains.

How to connect: add OpenMasu to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):

{
  "mcpServers": {
    "openmasu": {
      "url": "https://platform.openmasu.com/mcp",
      "headers": { "Authorization": "Bearer bpat_…" }
    }
  }
}

Without headers, Cursor offers to sign in with OAuth; OpenMasu accepts Cursor’s callback.

Create a tokenCursor MCP docs

What it does: any client that speaks the Model Context Protocol over Streamable HTTP can use OpenMasu: VS Code, your own agent or a script.

• Endpointhttps://platform.openmasu.com/mcp
• TransportStreamable HTTP (JSON-RPC 2.0)
• Sign-inAuthorization: Bearer <token>, or OAuth 2.1 discovered from /.well-known/oauth-protected-resource
• Tools52; the destructive ones ask for confirm: true, and undo reverts this session’s own changes

Create a tokenAbout MCP

What it does: skills are instructions (SKILL.md) that teach your agent to do a job well. The catalog has 37: 16 hosted by OpenMasu (how to work with OpenMasu, analysing your synced Stripe data, setting up a CRM, plus video and marketing skills) and 21 listings from Anthropic, Stripe, Vercel, Supabase, Cloudflare and Remotion, which link to their own repositories.

How to use them: browse them in the app (your workspace › Marketplace › Skills), ask your agent (tools list_skills and get_skill), or install a hosted one:

npx skills add https://platform.openmasu.com --skill openmasu

Open the marketplaceHosted skills index

What comes in: a new base, «Stripe · your account», with five linked tables:

• Customersname, email, phone, country, created, and their payments, invoices and subscriptions
• Paymentsdescription, amount, currency, status (paid, pending, failed), refunded, customer, date
• Invoicesnumber, customer, amount, status (draft, open, paid, void, uncollectible), date, due date, link
• Subscriptionsproduct, customer, status, monthly amount, start, next charge, cancelled on
• Productsname, active, description

Amounts arrive in normal units with each currency’s decimals (yen without decimals). Every record keeps its Stripe ID.

How to connect: in the Stripe Dashboard, go to Developers › API keys and create a restricted key named «OpenMasu» with Read access to Customers, Charges, Invoices, Subscriptions, Products and Prices. Paste it (rk_live_… or rk_test_…) under Marketplace › Stripe › Connect.

Open the marketplaceStripe API keys

What comes in: a new base, «SumUp · your business», with two linked tables:

• Salescode, date and time, amount, status, type (payment, refund, chargeback), channel (card reader or online), method (contactless, chip, Apple Pay, Google Pay…), card brand, description, refunded, served by
• Payoutsreference, date, gross, fee, paid out, status, type, and the sale it belongs to

Times use the time zone of your business’s country.

How to connect: in SumUp, open Profile › For developers › API keys, create a secret key named «OpenMasu» and paste it (sup_sk_…) under Marketplace › SumUp › Connect.

Open the marketplaceSumUp API keys

What it does: a one-time copy of an Airtable base into a new OpenMasu base (it does not stay in sync). It brings tables, fields, records, select options with their colors, two-way links, autonumbers, created and modified times, and grid views with their column order and visibility, keeping Airtable’s IDs. Formulas, lookups, rollups, attachments, collaborators and other unsupported fields arrive as long text with their visible value, and the result lists them. Airtable’s public API doesn’t expose view filters, sorts or groups, so those aren’t copied; kanban, calendar and other views are skipped.

How to connect: create an Airtable personal access token with the data.records:read and schema.bases:read scopes. Then ask your AI agent, for example «Import my Airtable base appXXXXXXXXXXXXXX into my workspace» (tool import_airtable), or call POST /api/import/airtable. The token is only used while the import runs and is never stored.

coming soon An import button inside the app.

Create an Airtable tokenConnect an AI agent

What it does: any form view can be shared as a public link (platform.openmasu.com/shr…). Anyone can fill it in without an account; each answer becomes a record and appears live for everyone with the base open. The public page only shows the form’s fields, never your records. Required fields are checked, bots are filtered out, and after sending you can redirect to your own page.

How to connect: create a form view in a table and press Share form to get the link. You can turn the link off at any time.

Open the app

What it does: JSON over HTTPS under https://platform.openmasu.com/api, authenticated with Authorization: Bearer. It covers workspaces and members, bases, Airtable imports, integrations (connect, sync, disconnect), public form links, version history and the skills catalog. Error messages come in English or Spanish according to Accept-Language.

curl https://platform.openmasu.com/api/bases \
  -H "Authorization: Bearer bpat_…"

To read and write records, use the MCP endpoint above (any HTTP client can call its tools) or the real-time WebSocket our apps use. A public REST reference for records is not published yet.

Create a tokenAsk us about the API

What it does: a token (bpat_…) works across the REST API, the WebSocket and MCP. Choose read (nothing can be changed) or write, optionally limit it to one workspace (everything else then looks as if it didn’t exist) and give it an expiry date. The value is shown only once. Revoking a token cuts access on the next request and closes its open connections. Up to 100 tokens per account.

How to connect: in the app, Account › API & tokens › create a token.

API & tokens

What it does: lets an app act for an OpenMasu user without handling their password. Authorization code with mandatory PKCE (S256), dynamic client registration (RFC 7591), read and write scopes, one-hour access tokens and 30-day refresh tokens that rotate. On the consent screen the user picks one workspace or all of them; they can revoke the app later in Connected apps.

• Metadatahttps://platform.openmasu.com/.well-known/oauth-authorization-server
• Redirectshttps, loopback http://127.0.0.1 (any port) and private app schemes

Server metadataConnected apps

What it does: the complete OpenMasu in any modern browser: all views, real-time collaboration, the marketplace and your account settings. The whole base loads into the browser and is computed there.

Start for freeLog in