ViablyViably
Viably MCP server

Your agent works Viably the way you do.

Connect Claude, Cursor or Codex and sign in once. The agent reads your inbox, the pipeline, the board and the relay logs, then claims contacts, moves deals and files tasks after you approve each change. It acts as you, so its work shows up in the dashboard and in Slack under your name.

Claude Code, Claude.ai, Cursor, Codex and your own scripts reach the workspace through Viably’s MCP server, as the member who signed in. Reads pass straight through, changes wait for the member to approve them, and every call is logged.
Your appsYour workspace
Inbox
Contacts
Deals
Tasks
Issues
Relay logs
Search and uptime
api.viably.app/mcp
Tool calls, as Jim
  • 14:01:58search_console_summaryRead
  • 14:01:46list_dealsRead
36
Tools, on every plan
1
Command to connect Claude Code
0
Tools that can message a customer
Connect

Add the server, then sign in as yourself.

Each app adds Viably with one command or one config entry, then opens a Viably sign-in in your browser. You pick the workspace, see what the agent may read and change, and approve. The app keeps its own token and renews it.

Terminal
$
viably.app/oauth/authorize
The sign-in opens here
  1. 1Add the server
  2. 2Sign in
  3. 3Ask

One command adds the server. Run /mcp inside Claude Code, pick viably, and approve the sign-in it opens.

Watch it work

What the agent changes lands where your team already looks.

Each change runs the dashboard's own write as you. A claimed contact shows you as its owner, a filed task posts its card to Slack, and a replayed event reaches its channel again. The audit trail records every one with the app that made it.

Claude Code, ~/athlead
Your workspace
M

Michael Scott

[email protected]
Waiting 2 days
SourcePricing form
OwnerUnclaimed
Draft reply, not sent
Hi Michael, annual billing covers every seat in the workspace, so adding the Scranton team changes nothing on the invoice.

Changes

API and agents

    The saved triage prompt reads your queue, shows a plan, and asks before each change. The reply stays a draft on the record, because sending it is yours.

    What it can reach

    Reads start ticked. Changes wait until you tick them.

    Each area of the workspace is a scope you grant at sign-in, and an agent that holds only reads cannot change a thing. The consent screen below works: tick a change and watch which tools it opens.

    viably.app/oauth/authorize

    Connect Claude Code to Viably

    Untick anything it does not need. Try it.
    What it can read
    What it can change
    20of 36 tools it can call
    Reads only, so it cannot change a thing
    Reads
    • whoami
    • search
    • list_inbox
    • find_contacts
    • get_contact
    • list_deals
    • list_tasks
    • list_issues
    • get_issue
    • list_pins
    • query_relay_logs
    • relay_endpoints
    • medal_leaderboard
    • list_events
    • list_reminders
    • search_console_summary
    • social_summary
    • uptime_status
    • github_activity
    • list_channels
    Changes
    • create_task
    • update_task
    • create_issue
    • resolve_issue
    • claim_contact
    • set_contact_status
    • tag_contact
    • add_contact_note
    • open_deal
    • move_deal
    • dismiss_inbox_item
    • snooze_inbox_item
    • set_reminder
    • cancel_reminder
    • create_event
    • replay_relay_event
    No scope reaches these
    • Reply to a customer
    • Merge or block contacts
    • Change billing
    • Change members or powers
    • Give medals
    • Your role and no more

      Every call runs through the same permission checks as the dashboard, as you. Scopes can narrow what the agent reaches.

    • A contact list counts as a download

      Listing names through find_contacts needs the download permission, and each list is logged under Downloads like any other export.

    • Outside text is treated as data

      Form fields, emails and webhook payloads reach the model as the agent works. Viably labels them as data in every result, and keeps your app asking before each change.

    Saved prompts, and records you hand over yourself

    The server ships three prompts that chain the tools the way a member works the dashboard. In Claude Code they are slash commands, like /mcp__viably__triage_inbox, and each one shows you its plan before it changes anything.

    Type @viably: to attach a contact waiting on a reply or an open issue. The record loads with its deals and timeline before the agent starts, masked the way your role masks it.

    What each prompt does
    Claude Code

    Claude reads your queue with list_inbox and proposes an ending for each item. First up: Michael Scott has waited two days on a reply.

    Type a slash for the saved prompts, which chain the tools the way you work the dashboard and mention only the changes your sign-in allows. Type @viably: to attach a person or an open issue, so the agent starts with the record in hand.

    Agents take turns, so the dashboard stays quick

    A workspace runs 2 tool calls at a time. The rest wait for up to 10 seconds, and a call that waits longer answers 503 with a Retry-After header, so an agent firing a burst slows itself down and nobody else.

    Tool calls count against the workspace’s monthly allowance: 500 on Free and 15,000 on Viably+, plus 3,000 for each top-up pack. Each token also gets 30 requests a minute on Free and 60 on Viably+, where a change costs 3.

    Limits and the audit trail
    api.viably.app, one workspace
    Waiting
    Running, 2 at a time
    list_inbox
    Free
    Answered
    Pick your agent

    Setup and stories for each app

    Every app reaches the same tools. Each page shows what that app is best at, from triaging the inbox in Claude to debugging a webhook in Cursor.

    FAQ

    Questions about the MCP server

    What is the Viably MCP server?
    A remote MCP server at https://api.viably.app/mcp that lists Viably's tools to any app that supports MCP over Streamable HTTP with OAuth. Your agent uses it to read and work your inbox, contacts, deals, tasks, issues, relay logs and reports, as you.
    Which apps can connect?
    Claude Code, Claude.ai, Cursor and Codex have setup steps in the guide, and any other app that signs in to remote MCP servers with OAuth works the same way. We test with Claude Code. Apps that cannot sign in can send a personal access token as a header.
    Can my agent see anything I can't?
    No. Every call runs as you, with your role, so a member whose role hides customer names gets them masked through the agent as well. The scopes you tick at sign-in can narrow that further.
    Can it email or message our customers?
    No tool sends anything to a customer. An agent can leave a draft reply as a note on the contact, and a person sends it from the dashboard or Slack.
    What if a customer's message tries to instruct my agent?
    Anyone who writes to your inbox puts text in front of the agent, and text written to look like an instruction can mislead a model. Viably labels that text as data, and no tool can reply to a customer. Keep your app asking before each change, and give an agent that runs unattended read scopes only.
    Does it cost extra?
    No. Every plan gets every tool. Free includes 500 tool calls a month and Viably+ 15,000, shared by the workspace, and each top-up pack adds 3,000 more.
    Ready when you are

    Ask your agent what is waiting on you.

    Start free, open API and agents, and copy the command for your app. Your inbox has an assistant the same afternoon.

    SignalRecordOwned work
    • Free to start
    • No credit card required
    • Powers on when you need them