Skip to main content
An MCP connector points Corvic at a remote Model Context Protocol server. Agents that are allowed to use the connector see the server’s tools and can call them like any other tool. The server’s credential stays in the vault. The catalog includes official MCP servers such as Jira (Atlassian) and Prior Labs (TabPFN). Selecting one opens Add MCP server with its address filled in.

​
Add an MCP server

1

Open the dialog

Choose Add Custom Connector → MCP server, or pick an MCP card in the catalog.
2

Enter the server URL

Paste the server’s address, for example https://mcp.example.com/mcp. Corvic contacts the server to find out how it signs in and which tools it offers. Nothing is stored until you confirm.
3

Sign in if the server asks

If the server shows OAuth required, Corvic registers itself with the server automatically when the server supports that. If it shows This server does not support automatic client registration, open Advanced — use your own OAuth client and paste the client ID (and secret, if any) you registered with the server.
4

Save

The connector appears under Connected with its sign-in state. Allow it for the agents that should use its tools.

​
Try tools before you build

Each room has an MCP Playground (in beta) where you can list a connected server’s tools, call one with your own arguments, and see the raw request and response.

Using connectors

Allow an MCP connector for an agent.

Corvic as an MCP server

The other direction: call Corvic from your own MCP client.