Skip to main content
Back to the Glyphic MCP server

MCP Gateway · Claude Cowork

Glyphic icon

Connect Glyphic to Claude Cowork

Cowork can take on sales analysis that spans dozens of calls and several drafts. With Glyphic synced in as a plugin, a session can read call transcripts, deal insights and conversation analytics, then produce a finished document. Speakeasy decides whether each prompt is allowed before the step runs, and OTLP telemetry from Cowork ties the work to the person who started it.

Category
Sales & CRM
Authentication
API key
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Glyphic MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glyphic call inspected and logged.

Deploy on MCP Gateway

Set up

Add Glyphic to Claude Cowork in 4 steps

  1. 01

    Add Glyphic from the catalog

    An admin finds Glyphic in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Glyphic authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Glyphic

    Give teams the mcp:connect scope on the Glyphic server through team access or a role. Claude Cowork connects to the Glyphic server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Glyphic from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Glyphic's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Glyphic

Write a win-loss analysis

Cowork reviews the quarter's closed deals, reads the key calls for each, and writes a win-loss report on why buyers chose you or walked away.

Build a battlecard from real calls

Ask Cowork to collect every sales call where a competitor came up, group the objections, and draft a battlecard with responses that worked.

Prepare an account handoff pack

When an account moves from sales to customer success, Cowork reads the deal's calls and insights and writes a handoff document covering goals, stakeholders and promises made.

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Glyphic call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Glyphic tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Glyphic can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Does the device agent cover Glyphic in Cowork?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies. Personal Claude accounts can't be governed in Cowork.
Do sales reps need GitHub access to use Glyphic in Cowork?
No. Members who receive plugins through Cowork don't need a GitHub invitation. Only the importing admin is added as a marketplace collaborator.
How do Claude Cowork users get Glyphic?
An admin adds Glyphic from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Glyphic tools their access allows.
Are Glyphic calls from Claude Cowork logged?
Yes. Glyphic calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Glyphic in other clients

AI everywhere.

Control here.