MCP Integration

Overview

SeggWat includes a built-in MCP (Model Context Protocol) server that enables AI assistants like Claude Desktop to interact directly with your feedback and rating data. This integration allows AI tools to:

Query feedback: List, search, and retrieve feedback items
Manage feedback: Create, update, and archive feedback
Access ratings: View and analyze helpfulness ratings
Automate workflows: Process feedback with AI-powered analysis
Generate insights: Analyze feedback trends and patterns

The MCP server is hosted at the /mcp endpoint and requires API key authentication.

Prerequisites

Before you start, ensure you have:

A SeggWat account with at least one project
An Organization Access Token (API key) - see API Integration
An MCP-compatible client (Claude Desktop, Cline, or other MCP clients)

The MCP endpoint uses the same API keys as the REST API. Keep your API key secure and never commit it to version control.

Setting Up Claude Desktop

1. Get Your API Token

Navigate to Settings

Generate Token

Go to the API Tokens tab and click Create New Token. Add a descriptive label like “Claude Desktop MCP”.

Copy Token

Copy the token immediately - it will only be shown once! You’ll use this in the next step.

2. Configure Claude Desktop

Add SeggWat to your Claude Desktop configuration file:

macOS
Windows
Linux
Self-Hosted

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "seggwat": {
      "type": "http",
      "url": "https://seggwat.com/mcp",
      "headers": {
        "Authorization": "Bearer oat_your_api_token_here"
      }
    }
  }
}

Edit %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "seggwat": {
      "type": "http",
      "url": "https://seggwat.com/mcp",
      "headers": {
        "Authorization": "Bearer oat_your_api_token_here"
      }
    }
  }
}

Edit ~/.config/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "seggwat": {
      "type": "http",
      "url": "https://seggwat.com/mcp",
      "headers": {
        "Authorization": "Bearer oat_your_api_token_here"
      }
    }
  }
}

For self-hosted SeggWat instances:

{
  "mcpServers": {
    "seggwat": {
      "type": "http",
      "url": "https://your-seggwat-domain.com/mcp",
      "headers": {
        "Authorization": "Bearer oat_your_api_token_here"
      }
    }
  }
}

3. Restart Claude Desktop

After saving the configuration, restart Claude Desktop to load the new MCP server.

4. Verify Connection

In Claude Desktop, try asking:

“List my SeggWat projects”

Claude should now be able to access your SeggWat data through the MCP server.

Available Tools

The MCP server provides the following tools:

Projects

list_projects

List all projects in your organization.Returns: Array of projects with IDs, names, and keys.

Feedback Management

list_feedback

List feedback with filtering and pagination.Parameters:

project_id (required)
page, limit (optional)
status, type, search (optional filters)

get_feedback

Get a single feedback item by ID.Parameters:

project_id (required)
feedback_id (required)

create_feedback

Create new feedback programmatically.Parameters:

project_id (required)
message (required)
type, source, path, version (optional)

update_feedback

Update feedback status, type, or message.Parameters:

project_id, feedback_id (required)
status, type, message (optional)

delete_feedback

Archive a feedback item.Parameters:

project_id, feedback_id (required)

Ratings Management

list_ratings

List helpfulness ratings with filtering.Parameters:

project_id (required)
page, limit (optional)
value, search (optional filters)

get_rating

Get a single rating by ID.Parameters:

project_id, rating_id (required)

create_rating

Create a new rating programmatically.Parameters:

project_id (required)
value (required, boolean)
path, version (optional)

delete_rating

Archive a rating.Parameters:

project_id, rating_id (required)

get_rating_stats

Get aggregated rating statistics.Parameters:

project_id (required)
path (optional, filter by page)

Usage Examples

Here are some common tasks you can perform with Claude Desktop connected to SeggWat:

Analyze Recent Feedback

“Show me the latest 10 feedback items from my main project and summarize the key themes”

Claude will:

List your projects
Fetch recent feedback
Analyze and summarize the content

Find Bug Reports

“Find all bug-type feedback from the last week that hasn’t been addressed yet”

Claude will:

Filter feedback by type=“Bug” and status=“New”
Present the results
Optionally help you prioritize them

Monitor Page Helpfulness

“What’s the helpfulness score for the /docs/getting-started page?”

Claude will:

Fetch rating statistics for that path
Calculate the helpfulness percentage
Show trends if available

Bulk Update Status

“Mark all feedback from yesterday as ‘In Progress’”

Claude will:

List feedback from the specified timeframe
Update each item’s status
Confirm the changes

Export for Analysis

“Create a markdown report of all high-priority feedback from this month”

Claude will:

Fetch filtered feedback data
Format it as a structured markdown report
Include relevant metadata and statistics

Authentication Options

The MCP server supports two authentication methods:

Bearer Token (Recommended)

{
  "headers": {
    "Authorization": "Bearer oat_your_api_token_here"
  }
}

API Key Header

{
  "headers": {
    "X-API-Key": "oat_your_api_token_here"
  }
}

Both methods are equivalent - use whichever fits your client’s configuration style.

Security Best Practices

Use dedicated API tokens

Create a separate API token specifically for MCP access. This allows you to revoke MCP access without affecting other integrations.Label it clearly: “Claude Desktop MCP” or “AI Assistant Access”

Protect your config file

The Claude Desktop configuration file contains your API key. Ensure it has appropriate file permissions:

# macOS/Linux
chmod 600 ~/Library/Application\ Support/Claude/claude_desktop_config.json

Monitor API usage

Check the “Last Used” timestamp in your dashboard to monitor MCP server access and identify any unexpected activity.

Rotate tokens periodically

Regularly rotate your API tokens (e.g., every 90 days) and update your MCP configuration accordingly.

Troubleshooting

Connection Issues

Problem: Claude Desktop can’t connect to SeggWat MCP server

Verify URL

Ensure the URL is exactly https://seggwat.com/mcp (no trailing slash)

Check API Token

Verify your API token is valid in the SeggWat dashboard under Settings → API Tokens

Test Manually

Test the connection with curl:

curl -X POST https://seggwat.com/mcp \
  -H "Authorization: Bearer oat_your_token" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Review Logs

Check Claude Desktop logs for error messages:

macOS: ~/Library/Logs/Claude/mcp*.log
Windows: %APPDATA%\Claude\logs\mcp*.log

Permission Errors

Problem: “Access denied” or 403 errors The API token might not have access to the requested projects. Ensure:

The token belongs to the same organization as the projects
The token hasn’t been revoked
Your account has appropriate permissions

Rate Limiting

Problem: “Too many requests” errors The MCP endpoint uses the same rate limits as the REST API:

20 requests per minute for feedback endpoints
If you hit limits, Claude will need to slow down its requests

Advanced Configuration

Custom Headers

Add custom headers for tracking or debugging:

{
  "headers": {
    "Authorization": "Bearer oat_your_token",
    "X-Client-Name": "Claude-Desktop",
    "X-Client-Version": "1.0.0"
  }
}

Using with Other MCP Clients

While this guide focuses on Claude Desktop, the SeggWat MCP server works with any MCP-compatible client:

Custom MCP Clients

For building custom MCP clients, see the Model Context Protocol specification. The SeggWat MCP server implements:

HTTP transport with streaming support
Standard MCP protocol (tools, resources, prompts)
Bearer token and X-API-Key authentication

Performance Considerations

The MCP server uses the same backend as the REST API, so performance characteristics are identical:

Average response time: < 100ms for list operations
Supports pagination for large datasets
Results are cached for 60 seconds

For optimal performance:

Use pagination (page and limit parameters)
Apply filters to narrow results
Cache project IDs locally in your workflows

Next Steps

API Reference

Complete API documentation (MCP tools mirror these endpoints)

API Integration

Learn about direct REST API integration

List Feedback

Detailed documentation for the list feedback endpoint

Rating Statistics

Learn about rating aggregation and analytics

General

API & Integrations

Frameworks

CMS

​Overview

​Prerequisites

​Setting Up Claude Desktop

​1. Get Your API Token

​2. Configure Claude Desktop

​3. Restart Claude Desktop

​4. Verify Connection

​Available Tools

​Projects

list_projects

​Feedback Management

list_feedback

get_feedback

create_feedback

update_feedback

delete_feedback

​Ratings Management

list_ratings

get_rating

create_rating

delete_rating

get_rating_stats

​Usage Examples

​Analyze Recent Feedback

​Find Bug Reports

​Monitor Page Helpfulness

​Bulk Update Status

​Export for Analysis

​Authentication Options

​Bearer Token (Recommended)

​API Key Header

​Security Best Practices

​Troubleshooting

​Connection Issues

​Permission Errors

​Rate Limiting

​Advanced Configuration

​Custom Headers

​Using with Other MCP Clients

​Custom MCP Clients

​Performance Considerations

​Next Steps

API Reference

API Integration

List Feedback

Rating Statistics

Overview

Prerequisites

Setting Up Claude Desktop

1. Get Your API Token

2. Configure Claude Desktop

3. Restart Claude Desktop

4. Verify Connection

Available Tools

Projects

Feedback Management

Ratings Management

Usage Examples

Analyze Recent Feedback

Find Bug Reports

Monitor Page Helpfulness

Bulk Update Status

Export for Analysis

Authentication Options

Bearer Token (Recommended)

API Key Header

Security Best Practices

Troubleshooting

Connection Issues

Permission Errors

Rate Limiting

Advanced Configuration

Custom Headers

Using with Other MCP Clients

Custom MCP Clients

Performance Considerations

Next Steps