TMCopilot MCP

Connect Claude, Codex, Gemini, or any MCP-capable agent to TMCopilot trademark tools and registry data.

How to Connect

Authenticate with API Key

Create an API Key in the Settings page, then add the following configuration to your MCP client:

{
  "mcpServers": {
    "tmcopilot": {
      "url": "https://mcp.tmcopilot.ai",
      "type": "http",
      "headers": {
        "X-API-Key": "your-api-key-here"
      }
    }
  }
}

Manage API Keys

Client Setup & Tools

Install TMCopilot in the client you actually use, then add the matching skill prompt so tool selection is stable.

Claude Code

The lowest-friction path for Claude is a project-scoped MCP server plus the shared TMCopilot skill prompt. After the CLI install, the team can share the same `.mcp.json`.

Install Server

claude mcp add --transport http --scope project \
  tmcopilot https://mcp.tmcopilot.ai

Install Canonical Skill

Use the tmcopilot MCP server as the default system of record for trademark, portfolio, competitor monitoring, office action, TTAB, owner, lawyer, and monitoring workflows.

Operating rules:
- Prefer TMCopilot tools over guessing from chat history when the request involves trademarks, office actions, competitor monitoring, owners, lawyers, reports, or portfolio status.
- Start narrow. If the user only wants counts, health, or status distribution, use summary tools first:
  - get_portfolio_summary
  - get_monitored_summary
  - get_portfolio_status_counts
- Use record-level list tools only when you need examples, ids, or a dataset:
  - list_portfolio_trademarks
  - list_office_actions
  - list_conflict_actions
  - list_cbp_recordations
  - list_upcoming_deadlines
- For competitor monitoring workflows, resolve profile context before deeper actions:
  - list_competitors
  - get_competitor
  - get_competitor_scan_results
  - list_competitor_activities
  - get_latest_competitor_report
- For mark text lookup, use search_trademarks. Do not use search_brand_owners for mark text.
- After search_trademarks, call get_trademark_details only for the serial numbers that actually matter to the user.
- For office action document review, follow this sequence:
  1. search_office_action_documents
  2. list_uspto_event_documents
  3. get_uspto_event_document_content
- For owner workflows, use search_brand_owners before list_brand_owner_trademarks.
- For lawyer workflows, use search_lawyers before search_lawyer_contact_info.
- Use fetch_all=true only when the user explicitly asks for whole-dataset analysis, bulk review, or complete exports.
- Before any write action, resolve ids and current state with read tools first.
- Treat action tools as approval-gated operations. Explain the intended change before using them:
  - trigger_office_action_scan
  - trigger_conflict_action_scan
  - trigger_cbp_scan
  - update_monitoring_config
  - batch_toggle_monitoring
  - import_portfolio_trademarks
  - update_trademark
  - update_office_action_status
  - update_conflict_action_status
  - batch_create_trademarks
  - create_competitor
  - update_competitor
  - delete_competitor
  - generate_competitor_report
  - get_competitor_report_share_link
- When updating monitoring, preserve the existing monitor configuration and change only the requested fields.
- When updating competitors, use owner_aliases only to add or reactivate aliases. Use exclude_owner_aliases only when the user explicitly wants aliases excluded.
- Never invent a portfolio trademark id, conflict action id, or office action id if a read tool can resolve it first.
- If a TMCopilot tool returns enough evidence to answer the question, do not keep calling adjacent tools without a clear reason.

Verify

claude mcp list

# inside Claude Code
/mcp