Glyphic + Claude MCP Integration
Last updated: April 19, 2026
Glyphic exposes an MCP (Model Context Protocol) server so Claude — Desktop or Code — can read your call data, summaries, and insights directly. Once configured, you can ask Claude questions like "summarize my last five calls" or "which deals had a competitor mentioned this month" and it will pull from Glyphic to answer.
What the MCP exposes
Call metadata
- Call ID, title, date, and duration.
- Participants (names, emails, organizations).
- Tags and call type.
- Recording and transcript availability.
Call content
- Full transcripts with speaker attribution and timestamps.
- AI-generated summaries.
- Key moments.
Insights
- Custom Insights (pain points, objections, qualification frameworks).
- Next steps and action items.
- Deal context and stage information.
- Sentiment.
Search and filter
- Date-range filtering (
start_date,end_date). - Participant-based search.
- Tag and insight filtering.
- Full-text search across transcripts and summaries.
- Semantic (vector-based) search.
Prerequisites
- An active Glyphic account with admin access.
- Claude Desktop (macOS) or Claude Code (terminal).
Step 1: Generate an API key
- Log in to Glyphic.
- Go to Settings → API.
- Click Create New Key.
- Give the key a descriptive name, e.g. MCP — Production.
- Copy the key and store it securely. The full key is only shown once.
For more on key management — limits, rotation, and revocation — see Managing API Keys.
Step 2: Configure Claude Desktop (macOS)
- Open Claude Desktop.
- Go to Settings / Preferences → MCP Servers / Integrations.
- Add the MCP configuration using the latest snippet from Settings → API in Glyphic. The snippet includes the package version, environment variables (with your API key), and connection settings.
- Restart Claude Desktop.
To verify, ask Claude: "List my recent calls." If the integration is configured correctly, it should return calls from your Glyphic workspace.
Step 3: Configure Claude Code (terminal)
- Make sure Claude Code is installed and authenticated.
- Open your config file (commonly
~/.claude/config.json). - Add the MCP server configuration from Settings → API in Glyphic.
- Restart your Claude session.
The exact configuration may differ slightly per environment. Always copy the latest snippet from Glyphic — older snippets may stop working when the MCP server is updated.
Step 4: Test it
Try a few simple queries to confirm API connectivity, data access, and configuration:
- "Show my recent calls."
- "Summarize my latest customer conversations."
- "What objections are coming up most frequently?"
Example use cases
- Call review — "Summarize my last five calls", "What were the key themes this week?"
- Customer insight — "What are the most common pain points?", "What objections are appearing in deals?"
- Deal intelligence — "What are the next steps across my active deals?", "Which deals are at risk?"
- Product feedback — "What features are customers requesting?"
- Cross-call analysis — "Compare enterprise vs mid-market conversations."
Troubleshooting
No data returned
- Check the API key is valid and hasn't been revoked.
- Confirm the MCP configuration was added correctly.
- Make sure there are calls in Glyphic the key has access to.
Connection errors
- Restart Claude.
- Verify the configuration syntax.
- Confirm environment variables are set correctly.
Outdated configuration
Use the latest setup snippet from Settings → API in Glyphic. The MCP server is updated periodically and older snippets may stop working.
If you have questions about the MCP integration, reach out to support@glyphic.ai.