Skip to content

Model Context Protocol (MCP)

MCP servers are the bridge between Seer agents and the external data sources they need to perform their jobs.

Available Servers

The system currently integrates with three primary data sources:

Server Purpose Tools Provided
BigQuery Seer Signals data Querying organic rankings, traffic data, and SERP snapshots.
DataForSEO Market research SERP analysis, keyword discovery, and competitor metrics.
Wrike Project management Task management, time tracking, and project status updates.

Location and Documentation

All MCP-related configurations and documentation are located in plugins/infrastructure/mcp-servers/.

  • Root Documentation: plugins/infrastructure/mcp-servers/README.md
  • BigQuery Details: plugins/infrastructure/mcp-servers/bigquery/README.md
  • DataForSEO Details: plugins/infrastructure/mcp-servers/dataforseo/README.md
  • Wrike Details: plugins/infrastructure/mcp-servers/wrike/README.md

Building MCP-Enabled Workflows

When building commands that rely on MCP data, follow these best practices:

1. Graceful Degradation

Always check if the required tools are available before attempting an operation. If a server is missing or misconfigured, provide a helpful error message and, if possible, a fallback path (e.g., "Manual input required" or "Proceeding with limited data").

2. Context Efficiency

MCP responses can be large. Use specialized tools or filters to request only the specific data needed for the task to avoid overwhelming the context window.

3. Security and Credentials

  • Never commit credentials: All API keys and tokens must be stored in environment variables (e.g., .env file).
  • Least Privilege: Use read-only credentials whenever possible.
  • Environment Mapping: Ensure your local .claude/.mcp.json or equivalent config correctly maps the environment variables to the server arguments.

Adding New Servers

To add a new MCP server to the infrastructure:

  1. Create a new directory in plugins/infrastructure/mcp-servers/.
  2. Add a comprehensive README.md documenting:
    • Authentication and environment variables.
    • Available tools and resources.
    • Example queries.
    • Troubleshooting steps.
  3. Register the server in the appropriate plugin manifests or global configuration files.

Reference

For more information on the Model Context Protocol, visit modelcontextprotocol.io.