@fragmentfit/mcp-server
v1.0.1
Published
MCP server for Fragment meeting intelligence
Keywords
Readme
@fragmentfit/mcp-server
MCP server that gives AI assistants — Claude Desktop, Claude Code, Cursor — read access to your Fragment meeting intelligence data.
How it works
This package runs as a local process on your machine. When an AI assistant needs to answer questions about your meetings, feedback, or themes, it calls this server over stdio. The server translates those requests into Fragment API calls using your API key.
┌─────────────────┐ stdio ┌──────────────────┐ HTTPS ┌─────────────────┐
│ Claude Desktop │ ◄────────────► │ fragment-mcp │ ◄───────────► │ Fragment API │
│ Claude Code │ MCP proto │ (this package) │ REST calls │ api.fragment.fit│
│ Cursor │ │ runs locally │ │ │
└─────────────────┘ └──────────────────┘ └─────────────────┘Prerequisites
- Node.js 22 or later
- A Fragment API key
Get your API key
- Open Fragment → Settings → API Keys
- Click Create API Key
- Copy the key or download the key file — you only see it once
- The key starts with
frag_live_
Setup
Claude Code
claude mcp add fragment -e FRAGMENT_API_KEY=frag_live_YOUR_KEY_HERE -- npx -y @fragmentfit/mcp-serverIf you downloaded the key file:
API_KEY=$(grep '^frag_' ~/Downloads/YOUR_KEY_FILE.txt)
claude mcp add fragment -e FRAGMENT_API_KEY=$API_KEY -- npx -y @fragmentfit/mcp-serverVerify it's connected:
claude mcp listThen start a conversation and ask Claude: "List my recent sessions using Fragment".
More options:
# Project-scoped (only available in this project)
claude mcp add fragment -s project -e FRAGMENT_API_KEY=frag_live_... -- npx -y @fragmentfit/mcp-server
# Remove the server
claude mcp remove fragmentClaude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"fragment": {
"command": "npx",
"args": ["-y", "@fragmentfit/mcp-server"],
"env": {
"FRAGMENT_API_KEY": "frag_live_..."
}
}
}
}Restart Claude Desktop. Click the hammer icon in the chat input to see the 15 Fragment tools.
Cursor
Add to Cursor Settings → MCP Servers:
{
"fragment": {
"command": "npx",
"args": ["-y", "@fragmentfit/mcp-server"],
"env": {
"FRAGMENT_API_KEY": "frag_live_..."
}
}
}Available tools
| Tool | What it does |
|------|-------------|
| list_sessions | List meetings with pagination, search, and folder filtering |
| get_session | Get full details for a single meeting (meta-analysis, participants) |
| get_session_transcript | Get the full meeting transcript |
| get_speaker_transcript | Get the transcript with speaker names identified |
| search_feedbacks | Search and filter feedback items across meetings |
| get_feedback | Get a single feedback item with full details |
| list_themes | List extracted themes and patterns from your feedback |
| get_theme | Get theme details including recommendations and related themes |
| get_company_context | Get your organization's company context |
| list_companies | List all companies/accounts in your organization |
| list_tags | List tags used to categorize feedback |
| list_folders | List folders used to organize sessions |
| get_notes | Get notes and annotations for a specific session |
| get_stats | Get aggregate stats (feedback and session counts) |
| get_usage | Get feedback type breakdown across session types |
All tools are read-only. They cannot modify your data.
Example prompts
Once connected, try asking your AI assistant:
- "List my recent sessions"
- "Show me the transcript for session [name]"
- "What are the top themes from my meetings?"
- "What feedback came from [company name]?"
- "Summarize the key insights from last week's sessions"
- "What are the most common pain points across all feedback?"
Troubleshooting
| Problem | Fix |
|---------|-----|
| Server not connecting | Run claude mcp list to check status. Re-run the claude mcp add command if needed. |
| "Authentication failed" | Your API key is invalid or expired. Create a new one in Fragment → Settings → API Keys. |
| "FRAGMENT_API_KEY environment variable is required" | The API key wasn't passed. Re-run claude mcp add with the -e FRAGMENT_API_KEY=... flag. |
| Tools return errors | Verify your Fragment account is active and you have data in your workspace. |
Environment variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| FRAGMENT_API_KEY | Yes | — | Your Fragment API key (starts with frag_live_) |
| FRAGMENT_API_URL | No | https://api.fragment.fit | Fragment API base URL |
