Schemas
Expose a schema over MCP
The MCP Server tab shares a schema with AI assistants over MCP, the Model Context Protocol. An MCP-capable assistant, such as an AI coding tool, can then look up your tables, columns, views and relationships while it helps you.
In the app: Data Model › Schemas › your schema › MCP Server tab
It shares schema metadata only: names, columns, types, descriptions and relationships. It doesn’t connect to a database and never exposes data.
Before you start¶
The tab’s settings are only visible to people with Read/Write access to the schema.
Turn the server on¶
- Open the
MCP Servertab. It is headedMCP Server Configuration. - Under
Server Settings, switch onEnable MCP Server. - Copy the
MCP Server URLwith the button beside it, and add it to your MCP client.
Switch it off to stop serving the schema.
Choose what the server shares¶
Under Enable Features in MCP Server, each kind of object has a sub-tab and a switch:
Tables:Enable Tables in MCPViews:Enable Views in MCPStored Procedures:Enable Stored Procedures in MCPFunctions:Enable Functions in MCPRelationships:Enable Relationships in MCPshares the foreign keys between tables.
For tables, views, stored procedures and functions, once a kind is enabled you can share all of them (Allow All Tables, Allow All Views and so on) or turn that off and tick exactly which objects the assistant may see.
Tip: Start narrow. Enable only the object kinds an assistant needs, and leave sensitive tables or internal procedures off the list. You can widen access later.
Regenerate the URL¶
If the URL has been shared too widely, click Regenerate URL and confirm. Kenseme issues a new URL. Every client using the old one stops working until you give it the new URL. This can’t be undone.
See who has used it¶
Expand Recent activity to see recent calls to the schema’s MCP server: When, Tool, User, Detail, Outcome, Rows and Duration. Until someone connects, it says No activity yet.