Read the whole picture
Voice profile, CRM contacts, lead lists, campaigns, approvals, posts and cached trend ideas.
Customer beta · controlled rollout pending
Model Context Protocol
Give your AI agent a safe way into Coldvio.
Connect a customer-owned Coldvio workspace to Claude, Codex, GitHub Copilot, VS Code and other MCP clients. The agent gets useful context and bounded actions—not unrestricted dashboard access.
Works with: Claude · Codex · GitHub Copilot · VS Code · stdio MCP clients
coldvio mcp
$ npx -y @coldvio/[email protected] login ✓ Signed in as [email protected] $ codex mcp add coldvio -- npx -y @coldvio/[email protected] mcp ✓ Added global MCP server coldvio $ codex mcp list ✓ coldvio · enabled · 17 tools
17
focused tools
4
guarded scopes
0
credentials in prompts
What you can do
Useful enough for real work. Narrow enough to trust.
The MCP surface follows the customer workflow from context to reviewed action. It deliberately excludes generic execute, direct send and direct publish tools.
Prepare work in your voice
Generate LinkedIn and email drafts with the same living voice profile used inside Coldvio. Draft generation never sends.
Review consequential actions
Update selected CRM fields or approve one existing campaign action only after an exact confirmation.
Set up
From install to a useful answer in minutes.
Version one runs locally over stdio, so the customer credential stays on the customer device while the agent speaks the open MCP protocol.
Sign in once
Browser PKCE connects the CLI to the customer’s own Coldvio account.
Add the local server
Start the versioned npm package from the MCP client’s user-level configuration.
Ask in natural language
The client discovers the 17 tools and selects the smallest useful read or confirmed action.
Copy this to Claude Code or Codex
Set up Coldvio MCP for me. 1. Run `npx -y @coldvio/[email protected] login` and let me finish browser sign-in. 2. Add the user-level stdio MCP server with `npx -y @coldvio/[email protected] mcp`. 3. Verify that `get_summary` is available. 4. Do not change, generate, approve or reject anything during setup.
The package is pinned to 0.1.0 so the setup stays reproducible. It becomes installable when the controlled customer rollout publishes the package.
Customer access by design
An agent connection should not become a master key.
Coldvio uses a dedicated customer Agent API, purpose-bound credentials and confirmation at the points where work changes state, spends credits or can reach LinkedIn.
Customer identity
The customer signs in with their own Coldvio account and reviews the requested access.
Tenant isolation
Every API query is scoped server-side to the signed-in customer—not to an ID supplied by the agent.
Purpose-bound access
Dedicated agent routes reject dashboard and browser-extension sessions.
Explicit confirmation
CRM writes, generation, approvals and rejections require confirmation for that exact operation.
Go deeper
From first login to production-safe patterns.
Explore product guides, exact client configuration, all 17 tools, the OpenAPI contract, security boundaries, use cases and troubleshooting in Coldvio Docs.