Connect Continue.dev
Add Pact as an MCP server in Continue's config.yaml so your assistant can query your CRM — consent-filtered and audited.
Continue supports MCP servers over Streamable HTTP in its YAML config, so Pact's tools are available to Continue's agent mode in a few lines. Every call is consent-filtered, tenant-scoped, and written to your Pact audit log.
Prerequisites
- A scoped Pact API key (
pact_live_*orpact_test_*), created at Settings → API keys, with the read scopes for the tools you want. - Continue (VS Code or JetBrains) with MCP support — any recent release.
1. Add the server
Edit ~/.continue/config.yaml (or your workspace's .continue/config.yaml)
and add an mcpServers entry:
mcpServers:
- name: Pact
type: streamable-http
url: https://api.pact.place/mcp/
requestOptions:
headers:
Authorization: Bearer pact_live_xxx
Replace pact_live_xxx with your key.
Warning
Keep the trailing slash on /mcp/ — the redirect from /mcp drops the Authorization header in
most HTTP clients and reads as a 401.
Note
MCP tools run in Continue's agent mode — in chat-only mode the server connects but tools aren't offered to the model.
2. Reload
Continue watches its config file; saving is usually enough. If the server doesn't appear, reload the IDE window (VS Code: Developer: Reload Window).
3. Verify
In agent mode, ask:
Using the Pact tools, which deals slipped their close date this month?
You should see a query_slippage call in the tool activity, and the response
reports any records hidden by consent (consent_filtered).
Troubleshooting
| Symptom | Likely cause |
|---|---|
| 401 on every call | Missing trailing slash, or a revoked key |
| Server connects but the model never uses tools | You're in chat mode — switch to agent mode |
| Scope error on a specific tool | The key lacks that tool's scope — see the tool reference |
Test any tool with real arguments — no LLM in the loop — in the tool sandbox before wiring up a client.