An MCP server for your databases.
Your field notes, client preferences, lyrics and workout logs are more useful when your assistant can work with them. Connect your Saytabase account to an MCP-compatible client and ask questions about the records you actually saved.
What is an MCP server?
An MCP server exposes tools and data to AI applications using the Model Context Protocol. Instead of pasting the same notes into every conversation, a compatible assistant can request the information it needs through a defined set of tools.
Saytabase hosts the server for you. You capture information by voice or text, Saytabase organizes it into database records, and your connected assistant can inspect the columns, search entries and store new structured records. You can still view and work with your data right here in the app.
Connect to the Saytabase MCP server
Create a Saytabase account and save a database first. Use this remote server URL in a client that supports remote MCP servers and OAuth authorization.
https://saytabase.xyz/mcpAuthorize with your Saytabase account when your client prompts you.
ChatGPT
- Open ChatGPT's connector settings and create a custom connector named Saytabase.
- Enter the server URL above as the remote MCP server address.
- Publish the connector, sign in with your Saytabase account when prompted, then turn the connector on in your chat.
- Ask: “List my Saytabase databases, inspect my client book, and find the clients who want a home office.”
Custom connectors need a ChatGPT plan with connector access, and the connector must be published before it appears in a conversation.
Claude
- Open Claude's settings and look for Connectors.
- Add a custom connector named Saytabase and enter the server URL above.
- Complete the authorization prompt, then enable the connector in your conversation.
- Ask: “List my Saytabase databases, inspect my fitness log, and find my recent runs.”
Custom connector availability depends on your Claude plan and workspace permissions.
Cursor & other MCP clients
In Cursor, add Saytabase under MCP settings, using the configuration below. Complete sign-in when prompted and enable the server's tools. Other clients need support for a remote HTTP MCP server and its authorization flow.
{
"mcpServers": {
"saytabase": {
"url": "https://saytabase.xyz/mcp"
}
}
}This is client configuration, not an API key. No local database server is required.
What your assistant can do
Start by listing databases, then inspect the schema before querying. Columns can evolve as you capture new kinds of information.
| Tool | Purpose |
|---|---|
| list_vaults | Discover the databases available to your authorized account. |
| get_vault_schema | Inspect a database's columns before searching or writing. |
| query_vault | Search the 200 newest records using keyword matching; return up to 50 results (10 by default). |
| store_memory | Save a flat map of text, number or boolean values as a new record; unknown field names create columns. |
Tool arguments & search limits
Use a database name or ID as vault. For example, your client can call query_vault with these arguments:
{
"vault": "Client Book",
"query": "home office",
"limit": 20
}The account-level server uses text matching, not a full SQL engine or exhaustive historical search. An empty query returns recent records. These four tools do not update or delete existing rows. To write, pass vault, a flat data object, and an optional summary to store_memory. Reuse existing column names to avoid unintended new fields.
Try a grounded request
“Inspect my client database, find clients who want a home office, and summarize their other preferences. Tell me if those details aren't in my records.”
Authorization, privacy & integration choices
The account-level MCP connection uses OAuth rather than a database key pasted into your prompt. Review the authorization request and the tools you enable: this connection can read records and write new ones, so it is not a read-only share link.
When you request an answer, relevant database information is sent to the assistant service you connected. Its data-handling terms also apply. Never put a private database key in a public document or chat.
MCP is for assistants that understand its tool protocol. The REST API is for applications that need direct HTTP access to database records and schema. Public forms are a separate, write-only way to collect submissions. Choose the connection that matches the job; they are not interchangeable permissions.
Connection troubleshooting
- The server won't connect
- Check that the URL ends in /mcp, not /mcp-server. The latter is this guide. Use a current client with remote MCP and OAuth support; a client that only launches local commands cannot use this URL directly.
- My database isn't listed
- Check which Saytabase account you authorized and save the database to that account. Unsaved showcase previews are not account databases.
- The assistant can't find a column or answer
- Ask it to inspect the schema again and use the actual column names. Confirm the information is in your saved records; a connection does not create missing history.