Skip to content

Configuration Reference

Complete reference for configuration files and settings in Seer Agent Engine.

Seer MCP Connection (Practitioners)

For most users: No configuration needed. Seer MCP is centralized and uses OAuth.

  1. Connect to SEERMCP in Claude (Web) via Connectors → Manage Connectors
  2. Authenticate with your Seer Google Account
  3. Done!

See Connect to Seer MCP for step-by-step instructions.

Configuration Files (Builders)

These configs are for developers and builders working on agents-infra.

OpenCode Configuration

Location: .opencode/config.json

OpenCode-specific settings for provider configuration and model preferences.

{
  "provider": "anthropic",
  "model": "claude-sonnet-4-20250514"
}

Claude Desktop/CLI MCP Configuration

Location: ~/.claude/.mcp.json

For builders connecting to Seer MCP from CLI tools:

{
  "mcpServers": {
    "seer-mcp": {
      "url": "https://seer-mcp.run.app",
      "auth": {
        "type": "oauth",
        "provider": "seer"
      }
    }
  }
}

Plugin Manifest

Location: .claude-plugin/plugin.json

OpenCode (optional): .plugin/manifest.json

Defines plugin metadata and dependencies.

{
  "name": "seo",
  "version": "2.7.0",
  "dependencies": {
    "plugins": [
      { "name": "core-dependencies", "version": ">=1.0.0", "required": true }
    ]
  }
}

Environment Variables (Builders Only)

Practitioners don't need this

Seer MCP handles all data access via OAuth. The environment variables below are only for builders doing local development or working on MCP tools.

Local Development (Optional)

If you're developing locally and need direct API access:

Variable Purpose Who Needs It
WRIKE_ACCESS_TOKEN Direct Wrike API access Operations plugin developers

Setting Environment Variables

Add to your shell profile (~/.bashrc, ~/.zshrc, etc.): 

export WRIKE_ACCESS_TOKEN="your-access-token"
Then reload: source ~/.zshrc

$env:WRIKE_ACCESS_TOKEN = "your-access-token"

# Set permanently (User level)
[Environment]::SetEnvironmentVariable("WRIKE_ACCESS_TOKEN", "value", "User")

Create a .env file in your project root: 

# .env (DO NOT COMMIT)
WRIKE_ACCESS_TOKEN=your-access-token

Security

Never commit .env files to version control. Add .env to your .gitignore.

Verifying Configuration

For Practitioners

Test your Seer MCP connection:

  1. Start a new conversation in Claude
  2. Ask: "What tools do you have access to from Seer MCP?"
  3. You should see tools like seersignals_run_query, workflowlibrary_list_workflows

For Builders

Run the diagnostic command:

/core-doctor

This verifies:

  • Plugin loading status
  • MCP server connectivity
  • Authentication status

Troubleshooting

"Not connected to Seer MCP"

Cause Solution
Not in Seer workspace Switch to Seer Team Plan in Claude
OAuth expired Reconnect via Manage Connectors
New conversation needed Tools load at conversation start

"Command not found"

Platform Solution
Claude Code Use namespaced command: /seo:content-audit
OpenCode Use short name: /content-audit

Plugin Not Loading

  1. Verify core-dependencies is installed first
  2. Check plugin manifest syntax (valid JSON)
  3. Restart your session after installation

Security Best Practices

  1. Use Seer MCP - Don't store API credentials locally when possible
  2. Use OAuth - Seer MCP handles authentication securely
  3. Don't commit secrets - If using .env files, add to .gitignore
  4. Rotate keys - If you must use local credentials, rotate regularly

Reference

How-To

Specification

Last updated: 2026-01-26