Managed MCP Server

Tacnode includes a managed MCP Server with token-based authorization, schema inspection, and support for executing read-only queries. To access the MCP Server, a valid token is required.

Creating Tokens

Tokens associate SQL execution with specific computational resources (Nodegroup) and storage resources (Database), while granting valid permissions for your account in the selected database. Each token has a 180-day lifespan and cannot be used after it expires.

Token creation relies on platform services. First, enable Platform Service Authorization under Security -> Access Authorization.

To create a token, select the desired Nodegroup for SQL execution. In the Nodegroup Overview, click MCP Tokens to view existing tokens associated with your account.

Click Create Token, select the associated Database, and generate a new token.

To view token details, select the relevant token. You can copy this token and use it for MCP Client access.

Accessing the Tacnode MCP Server

Tacnode provides a managed MCP Server at https://mcp-server.tacnode.io/mcp, using the Streamable HTTP transport protocol. The examples in this guide use the MCP Inspector tool to simulate MCP Client requests. When configuring Authentication, enter a valid, non-expired token in the Bearer Token field. (Note: when using MCP Inspector with local proxy mode, you also need to configure the Proxy Token for MCP Inspector.)

MCP Server supports the Resources List and Resources Read interfaces for retrieving metadata details.

MCP Server supports the Tools List and Tools Call interfaces for executing read-only queries directly on the database.

For the complete API documentation, see Managed MCP Server API.