Trademarks MCP server
{
"mcpServers": {
"markmesh-trademarks": {
"type": "http",
"url": "https://markmesh.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"markmesh-trademarks": {
"type": "http",
"url": "https://markmesh.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"markmesh-trademarks": {
"type": "http",
"url": "https://markmesh.com/api/v1/mcp"
}
}
}{
"servers": {
"markmesh-trademarks": {
"type": "http",
"url": "https://markmesh.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"markmesh-trademarks": {
"type": "http",
"url": "https://markmesh.com/api/v1/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Search, monitor, and research trademarks across 30+ national and regional registers with source attribution. Intended for trademark lawyers, IP teams managing portfolios, and developers integrating trademark data into applications.
- Search multiple trademark offices for conflicting marks by name and Nice class to assess availability
- Monitor pending trademark filings for status changes and track expiry dates for portfolio management
- Import trademark records from office registers into your portfolio with verified provenance
Tools this server exposes
| Tool | Does |
|---|---|
| search_office | Search one or more trademark registers for marks by name |
| search_conflicts | Run conflict research against a shortlist of names scoped by Nice class |
| list_trademarks | List trademarks in your portfolio, optionally filtered by client |
| list_filings | List filings with renewal and expiry deadline information |
| list_clients | List clients in your organisation |
| import_filing_from_office | Import a filing from a trademark office into your portfolio |
| create_watch | Monitor a filing and receive updates when its status changes |
| watch_changes_since | Query what has changed in watched filings since a specified time |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.