Continue

Edit ~/.continue/config.json. Add to the mcpServers array:

Hosted (recommended)

{
  "name": "talonic",
  "url": "https://mcp.talonic.com/mcp",
  "headers": {
    "Authorization": "Bearer tlnc_your_key_here"
  }
}

Local (npx)

{
  "name": "talonic",
  "command": "npx",
  "args": ["-y", "@talonic/mcp@latest"],
  "env": {
    "TALONIC_API_KEY": "tlnc_your_key_here"
  }
}

Continue works across both VS Code and JetBrains IDEs, making Talonic tools available regardless of your editor choice. The mcpServers array in Continue's config supports multiple MCP servers, so Talonic runs alongside any other MCP tools you have configured.

After saving the config, reload your IDE window to pick up the changes. Continue discovers Talonic's eight tools and two resources automatically. You can verify the connection by asking the agent to call talonic_list_schemas — it should return your saved schemas or an empty list.

Continue's config format uses a name field instead of a key in the mcpServers object. Make sure to include "name": "talonic" in the entry. The rest of the config — command, args, env for local, or url and headers for hosted — follows the same pattern as other MCP clients.

Verify the connection

// Agent sends (no parameters needed):
{}

// Successful response confirms connection:
{
  "schemas": [
    {
      "id": "sch_7a1b...",
      "short_id": "SCH-A1B2C3D4",
      "name": "Standard Invoice",
      "field_count": 6
    }
  ]
}

Continue is ideal for teams that use both VS Code and JetBrains IDEs and want a consistent Talonic experience across editors. Because the config file is shared, a schema saved from a Continue session in IntelliJ is immediately available in a VS Code session — no extra setup needed. This cross-editor consistency extends to all Talonic tools, not just schemas.

When using Continue with the hosted Talonic server, the connection is established over HTTPS directly from the Continue extension. No local MCP process is spawned, which reduces resource usage in the IDE. For JetBrains users in particular, this avoids adding another background process alongside the already resource-intensive IDE. The local npx option remains available for offline work or when HTTPS connectivity is restricted.