Ask Codex what's stuck.
Two commands connect the Codex CLI to Viably. The session that edits your code can then read the pipeline, the board and the relay logs, and file the follow-up once you approve it.
which sales deals have stalled this month?
Dunder Mifflin is the largest of the five at $12,000, and nobody owns it. I can set a follow-up task for Friday in #sales and assign it to you.
Your workspace, as tools an agent can call.
The server lists these to any app that connects. Reads are ticked when you sign in, and each area of changes needs its own tick.
Inbox and contacts
A list shows names only to a member who may also download contacts, since an agent can page through the whole book.- list_inboxfind_contactsget_contactclaim_contactset_contact_statustag_contactadd_contact_notedismiss_inbox_itemsnooze_inbox_item
Deals
Stages come from your own pipelines, and list_deals returns the keys move_deal expects.- list_dealsopen_dealmove_deal
Tasks, issues and the calendar
A task or issue an agent creates posts its card to Slack, the same as one filed from the dashboard.- list_taskscreate_taskupdate_tasklist_issuesget_issuecreate_issueresolve_issuelist_eventscreate_eventset_reminder
Logs, search and signals
Replaying a relay event is for workspace admins.- query_relay_logsreplay_relay_eventsearch_console_summarysocial_summaryuptime_statusgithub_activitymedal_leaderboardsearchwhoami
Two commands and a tab you approve.
codex mcp add registers the server and codex mcp login opens a Viably sign-in. Pick the workspace, leave reads ticked, tick the changes you want Codex to make, and approve. Codex keeps the token and renews it.
- One entry in config.toml
Codex saves the server to ~/.codex/config.toml, and the Codex IDE extension reads it from there too.
- For headless machines
Create a personal access token on API and agents and send it as a bearer header. It carries the scopes you picked when you made it.
- Every change on the record
Each write is logged with you, the app, the tool and the record it touched, including the calls Viably refused.
Connect Codex to Viably
Codex will act in your workspace as you, limited to what your role allows. Untick anything it doesn’t need.
Your inbox
Contacts
Deals
Tasks
Issues
Claim contacts, set their status, tag them and add notes
Open deals and move them between stages
Create tasks, which post to Slack, and change their status, assignee and due date
Create issues and resolve them, noting it in their Slack thread
Production questions in the same session.
Codex can check uptime_status before a deploy, read github_activity for what merged this week, or search the relay logs for the payload that broke a handler. The answers come from the workspace your team already runs, so nobody pastes screenshots into the chat.
Viably
The same tools over plain HTTP.
Every tool the MCP server lists is also a REST endpoint at /v1/<tool>. A nightly job can read the inbox or open a task with a personal access token and curl, with no agent involved.
Read the API referenceEvery tool on every plan, counted by the call.
Free includes 500 tool calls a month and Viably+ includes 15,000, shared by the whole workspace. A top-up pack adds 3,000 more. Connecting a second app or a second teammate costs nothing extra.
Questions about the Codex integration
How do I add Viably to Codex?
Can I use it from CI?
Which tools will Codex see?
Can the agent see anything I can't?
Can it email or message our customers?
What if a customer's message tries to give the agent instructions?
What happens when someone leaves the workspace?
Connect something else
Everything lands in the same record, so the second service you connect takes less setting up than the first.
Let the terminal answer for the pipeline.
Once Viably is in your Slack, two commands connect Codex. Then ask it which deals have stalled.
- Free to start
- No credit card required
- Powers on when you need them