$ claude mcp add --transport http sillage https://api.getsillage.com/api/mcp/v2Field manual / For agents / MCP
Give your agents a sense of timing.
Signals for AI agents, through MCP. Claude, Cursor or your own agent asks, Sillage answers with what it detected on your accounts.
$ claude mcp add --transport http sillage https://api.getsillage.com/api/mcp/v2Pull-only, signals detected daily.
friends with
§ 01 / Install lines
One line, then your agent is connected
Point your client at the server URL and log in with Sillage. That is the whole setup.
$ https://api.getsillage.com/api/mcp/v2{ "mcpServers": { "sillage": { "url": "https://api.getsillage.com/api/mcp/v2" } }}
Any other MCP-compatible client works the same way: server URL, HTTP transport, Sillage login. Step by step in the install guide.
§ 02 / What the MCP exposes
Five bearings your agent can take
What your agent can do, grouped by purpose. Each one acts on the single workspace you authorized.
Set up your persona
$ Who you sell to, and what you sell
- Read the persona of your workspace
- Create or update it from a short interview
- Check what is left to set up
Build your lists
$ Customers and prospects, monitored
- Create customer and prospect lists
- Add or remove companies and people
- Turn monitoring on and follow where a list stands
Set up signals
$ Browse templates, pick what to watch
- Browse the signal templates
- Set up a signal on a list
- Edit or remove a signal setup
Launch and follow runs
$ Start a detection, watch it finish
- Launch a signal run on demand
- Follow its progress until it completes
- See what a run found
Read your results
$ Signals, leads, companies and credits
- Read signals, leads and companies
- Read generated contents
- Read account mappings and where they stand
- Check your credits and usage
Full reference, with what each tool does, in the tool reference.
§ 03 / Skills pack
Tools tell it what exists. Skills tell it how.
Short Markdown playbooks that install into your assistant and teach it to run a Sillage workspace safely.
$ npx skills add sillage-labs/skills- 01
sillage-onboarding
Turns a short interview about what you sell, who buys and the signals that matter into a precise persona and a set of signal setups.
- 02
sillage-manage-workspace
Sets up a new workspace and edits a live one safely: read, diff, patch.
- 03
sillage-help
Explains how a workspace fits together and defines every term, from persona to detections.
- 04
sillage-api
Drives the same workspace over the REST API with an API key, where the MCP cannot be installed.
§ 04 / Sample conversation
Ask in plain words, get a signal back
Illustrative session on a fictional account, Northwind Logistics.
You
Anything new at Northwind Logistics I should act on this week?
Agent
One signal, detected on the daily pass: Northwind Logistics has a new head of supply chain who joined from a competitor of yours. It matches your job-update signal setup on your Tier 1 accounts. A short note that names the move is a good opener, want me to draft it?
You
Yes, and tell me what is left to set up in the workspace.
Agent
Open by congratulating the move, then tie it to supply chain visibility. On setup, you are in good shape: the persona, your lists and your signal setups are all in place, nothing is blocking.
§ 05 / What it costs
Same credits as the platform, from the same wallet.
§ 06 / FAQ
Questions from agent builders
How does my agent authenticate?
With your Sillage login. When you connect a client you log in with your account and authorize one workspace, over OAuth 2.1. There is no API key to paste for the MCP. API keys are for the REST API, if you prefer plain HTTP.
Which data can my agent see?
Only the workspace you authorized: its persona, lists, signal setups, signals and generated contents. A connection maps to one workspace, with no cross-workspace access.
Does Sillage push anything to my agent?
No. The MCP is pull-only: your agent asks, Sillage answers. Signals are detected daily, and your agent reads what has been found whenever it calls the tools.
Which clients work?
Claude Code, Claude desktop and claude.ai, and Cursor are covered in the docs. Any MCP-compatible client works: point it at the server URL over HTTP and complete the Sillage login.
What does it cost?
The MCP itself is not a separate product. Actions that find signals or contact data use the same credits as the platform, from the same wallet.