MCP server setup

1. Register the MCP server from the terminal. Run this from the project folder where you use Claude Code, as the server is registered per project by default (see Claude Code MCP documentation):

   claude mcp add --transport http selectzero-catalog http://<selectzero-host>/api/v1/mcp

2. Open the generated config file (location is printed in the output) and add the authorization header:

   "selectzero-catalog": { "type": "http", "url": "http://<selectzero-host>/api/v1/mcp", "headers": { "Authorization": "Bearer <your-personal-access-token>" } }

3. Restart Claude Code. The catalog tools become available and Claude can query the data catalog conversationally, scoped to the token-owner's role and allowed connections.

VS Code added MCP support starting with version 1.99. GitHub Copilot Chat in Agent mode can use registered MCP servers.

1. Create a workspace MCP config file at .vscode/mcp.json in the project folder (or add to your user settings.json under "mcp" for a global config):

   { "servers": { "selectzero-catalog": { "type": "http", "url": "http://<selectzero-host>/api/v1/mcp", "headers": { "Authorization": "Bearer <your-personal-access-token>" } } } }

2. Open the Copilot Chat view, switch to Agent mode, and the SelectZero tools appear in the tool picker.

3. The token is stored in the config file; treat the file as a secret and exclude it from source control. VS Code also supports ${input:variableName} placeholders that prompt for the token on first use - see VS Code MCP documentation for the input syntax.

1. Open Cursor Settings -> MCP and press Add new MCP server, or edit ~/.cursor/mcp.json directly:

   { "mcpServers": { "selectzero-catalog": { "url": "http://<selectzero-host>/api/v1/mcp", "headers": { "Authorization": "Bearer <your-personal-access-token>" } } } }

2. Toggle the server on in the MCP settings panel. Tools appear in the Composer/Chat tool picker.

Microsoft 365 Copilot reaches the SelectZero MCP server via a Copilot Studio agent. End users chat with the agent inside the regular Microsoft 365 Copilot interface; the agent owner does the one-time setup in Copilot Studio.

Prerequisites:

• A Microsoft Copilot Studio license and access to Copilot Studio.

• The SelectZero MCP endpoint reachable from Microsoft's cloud (or via your tenant's connectivity solution, e.g. on-premises data gateway / Power Platform virtual network).

• A SelectZero PAT for the user identity the agent should run as.

Steps (UI labels current as of Copilot Studio 2026; see the Microsoft Learn guide for the authoritative walkthrough):

1. In Copilot Studio, open an agent (or create a new one). Make sure generative orchestration is enabled for the agent (required for MCP tools).

2. Open the Tools page, press Add a tool, then New tool, and select Model Context Protocol. The MCP onboarding wizard appears.

3. Fill in:

   • Server name - e.g. SelectZero catalog

   • Server description - a short description so the orchestrator knows when to invoke it (e.g. "Query the SelectZero data catalog: tables, columns, lineage, glossary, test cases.")

   • Server URL - http://<selectzero-host>/api/v1/mcp

4. Under authentication, select API key:

   • Type - Header

   • Header name - Authorization

5. Select Create. In the Add tool dialog, choose Create a new connection and provide the API key value as Bearer <your-personal-access-token> (include the literal Bearer prefix). Then Add to agent.

6. Publish the agent. End users select the agent inside Microsoft 365 Copilot chat and the SelectZero catalog tools become available conversationally.

The agent's MCP tool inherits the role and connection access of whichever user's PAT the connection was created with. If you need different users to see different slices of the catalog, configure the authentication differently (each user provides their own PAT via OAuth, or use a service-style PAT scoped narrowly).

SelectZero ships a Claude Desktop extension as a .mcpb package. The install dialog takes a SelectZero URL and a PAT; the extension handles stdio↔HTTP bridging internally. The mcp-remote JSON-config bridge below remains supported for environments that prefer it.

If your environment cannot install desktop extensions (locked-down corporate device management, kiosk mode, etc.), the community mcp-remote bridge is a JSON-config alternative. Functionally equivalent to the extension; just needs npx on your PATH.

1. Open the Claude Desktop config file:

   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

   • Windows: %APPDATA%\Claude\claude_desktop_config.json

2. Add the SelectZero MCP server entry:

   { "mcpServers": { "selectzero-catalog": { "command": "npx", "args": [ "-y", "mcp-remote", "https://<selectzero-host>/api/v1/mcp", "--header", "Authorization:Bearer <your-personal-access-token>" ] } } }

3. Restart Claude Desktop. The catalog tools appear in the conversation tool picker.

Any MCP-compatible client following the MCP specification should work against /api/v1/mcp with a Authorization: Bearer <PAT> header. Refer to the client's documentation for the exact config file location and syntax.

If your client does not support Streamable HTTP natively, the mcp-remote bridge shown in the Claude Desktop tab works generically for any stdio-only MCP client.