MCP server · Databases and warehouses

Quickbase MCP server

Quickbase in any MCP client, through Memtro: Quickbase does not publish this server. Memtro's Quickbase connector reads Quickbase through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Quickbase low-code database: an app's tables, each table's fields, records queried with Quickbase's query language, sorting and paging, and saved reports run as they are configured; when you ask, can add records, update records by Record ID, and delete records by Record ID.

Reads

  • quickbase_get_appA Quickbase app: name, description, when it was created and last changed, and its time zone and date format.
  • quickbase_list_tablesThe tables in a Quickbase app: table id (for every other tool), name, description, when its data last changed…
  • quickbase_list_fieldsThe fields of a Quickbase table: field id (records are read and written by it), label, type, whether it is a lookup, summary or formula…
  • quickbase_query_recordsRecords from a Quickbase table, with values under their field labels.
  • quickbase_list_reportsThe saved reports of a Quickbase table: report id, name, type (table, summary, chart and so on) and description.
  • quickbase_run_reportRuns a saved Quickbase report and returns its rows as the report defines them: records for a table report…

Acts, when you ask

These change something in Quickbase. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • quickbase_add_recordsAdds records to a Quickbase table, values by field id; the table's notifications and automations may fire, as for a person.
  • quickbase_update_recordsChanges fields on existing Quickbase records, found by Record ID; only the fields passed change, and the old values are overwritten.
  • quickbase_delete_recordsPermanently deletes Quickbase records by Record ID (up to 100, listed explicitly; never by query).

Connect it

First connect Quickbase on Dashboard → Connections, then add Memtro to your client once. The Quickbase tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Quickbase connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which tables are in our operations app?
  • › What fields does the Projects table have?
  • › Which open projects are due this month?
  • › Run the Overdue Invoices report.
  • › Set record 412 in Projects to Done.

Questions

Is this an official Quickbase MCP server?
No. It is Memtro's MCP server with Memtro's Quickbase connector behind it: the connector reads Quickbase through its API with the credentials you connect on Dashboard → Connections, and Quickbase publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Quickbase?
Only when you ask, and only what it has been granted: add records to a table; update records by Record ID; delete records by Record ID. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Databases and warehouses

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time