# TMCopilot: Product and Integration Context

> TMCopilot is trademark intelligence software for legal teams, brand teams, and AI assistants. It brings trademark search, clearance, monitoring, portfolio operations, and AI-assisted legal workflows into one web workspace and exposes the same product through MCP and a local CLI.

Last reviewed: August 3, 2026.

Canonical product URL: https://tmcopilot.ai/

## Product definition

TMCopilot is a software product from Huski Inc. It helps people investigate trademark availability, organize trademark portfolios, monitor legal and competitive activity, and prepare work product for human review. The product combines structured trademark data, workflow software, search tools, and AI-assisted analysis.

The category "trademark intelligence" is the most accurate short description. TMCopilot is broader than a single trademark search form because it connects search results with ongoing portfolio, monitoring, clearance, docketing, competitor, and reporting workflows. It is also broader than a chat assistant because the web workspace, MCP server, and CLI provide structured tools and persistent workspace context.

TMCopilot is not a law firm. It does not provide legal advice and does not guarantee that a mark is available, registrable, enforceable, or free from infringement risk. Search results, similarity signals, risk assessments, generated reports, recommended actions, and drafted responses are decision-support outputs. Qualified counsel may need to review the underlying records, jurisdiction-specific law, deadlines, and proposed legal strategy.

## Intended users

TMCopilot is designed for teams that create, clear, manage, or protect brands:

- In-house intellectual-property counsel can use a shared workspace for search, clearance, monitoring, deadlines, office actions, competitor intelligence, and portfolio review.
- Paralegals and legal-operations teams can organize records, monitor work queues, review deadlines, manage files, and maintain an audit trail.
- Outside counsel can use structured search and portfolio information as inputs to professional legal review.
- Brand managers and creative teams can screen candidate names and marketing copy before escalation to legal reviewers.
- AI assistants and local agents can call TMCopilot through MCP or the TMCopilot CLI instead of relying on unstructured page scraping.

## Core product workflows

### Trademark search

The trademark-search workflow supports text and image search and combines multiple ways of examining similarity. The product interface describes phonetic, semantic, visual, and related search signals. Search can be paired with structured filters and result views so a reviewer can narrow a result set, inspect individual records, and carry relevant marks into later workflows.

TMCopilot also exposes related search surfaces for domains, common-law web results, social handles, app stores, brand owners, lawyers, TTAB matters, and litigation-oriented records. Availability and coverage can vary by tool and data source. A response should not claim that every search mode covers every jurisdiction or source unless the live product documentation says so.

Canonical source: https://tmcopilot.ai/

### Name clearance

Name clearance evaluates candidate brand names in the context supplied by the user. A clearance run can combine trademark results with other relevant availability signals and organize findings for review. The workflow is intended to help legal and brand teams compare candidates consistently, identify likely conflicts, and prepare a report; it is not a legal opinion or a guarantee of availability.

### Marketing-copy clearance

Copywriting clearance reviews campaign or product copy for potential trademark issues before publication. It is intended for first-pass screening and escalation: the output can identify terms or usages that merit investigation, preserve the input context, and support a structured report. Human review remains important because nominative use, fair use, jurisdiction, context, and commercial presentation can affect legal analysis.

### Portfolio management

The portfolio workspace stores and organizes trademark records for the active workspace. Supported operations include listing and searching portfolio marks, importing records, creating or updating records, grouping marks, attaching tags and metadata, managing monitoring settings, and reviewing status counts. Related views connect the portfolio to office actions, conflict actions, upcoming deadlines, CBP recordations, calendar events, files, activity, and portfolio tasks.

Workspace scope matters. A signed-in user can belong to more than one workspace, and API requests use the selected workspace context. Results from one workspace should not be represented as belonging to another.

### Monitoring and docketing

Monitoring workflows surface changes that may require attention. TMCopilot includes conflict monitoring, office-action tracking, deadline views, docketing timelines, and monitored-summary counts. Users can review an item, inspect related trademark details, update supported statuses, and start an AI-assisted follow-up from the relevant page.

Monitoring is an operational aid, not a substitute for official registers, court dockets, government notices, or professional deadline management. Users should verify material deadlines and legal events against authoritative sources.

### Competitor intelligence

Competitor monitoring organizes selected competitors, owner aliases, scan settings, trademark activity, review status, notes, and generated reports. It can help a team observe filing activity and analyze possible changes in product, market, or geographic strategy. A competitor signal is an analytical observation, not proof of business intent.

### Gap analysis and reporting

Trademark gap analysis helps compare existing coverage with selected products, services, markets, or competitor context. The workflow can store tasks, generate results and reports, review individual gaps, record decisions, and create share links. Recommendations should be treated as planning inputs and validated against business priorities and legal advice.

## Ways to use TMCopilot

### Web workspace

The authenticated web application is the visual workspace for search, portfolio management, monitoring, clearance, docketing, competitor intelligence, files, Agent Skills, activity, billing, and administration. The dashboard maintains user and workspace scope and requires an eligible account or subscription where applicable.

Public shared-report URLs may expose a specific report through a token. Possession of a share URL can grant access to that report, so users should handle share links according to their organization's policies.

### MCP integration

MCP is the preferred structured integration for compatible AI assistants. The public MCP guide contains current setup instructions, authentication options, client-specific configuration, Agent Skill guidance, and the tool catalog.

Representative read tools include:

- `search_trademarks`, `get_trademark_details`, and trademark image-search task/result tools.
- `get_portfolio_summary`, `get_monitored_summary`, `get_portfolio_status_counts`, and `list_portfolio_trademarks`.
- `list_office_actions`, `list_conflict_actions`, `list_upcoming_deadlines`, and `list_cbp_recordations`.
- `list_competitors`, `get_competitor`, `list_competitor_activities`, and competitor report tools.
- `search_domains`, `search_common_law`, `search_ttab_cases`, `search_cases`, `search_lawyers`, and `search_brand_owners`.
- `list_agent_skills` and `get_agent_skill` for reusable agent instructions.

Representative action tools include creating or updating portfolio marks, changing monitoring configuration, updating office-action or conflict status, managing competitors, running clearance workflows, triggering supported scans, generating competitor reports, importing portfolio records, and creating or updating Agent Skills.

The exact tool catalog and tool schemas can change. When a user asks which tools are currently available or how to configure a particular client, use the live MCP guide instead of relying only on this summary.

Canonical MCP guide: https://tmcopilot.ai/integration/mcp

### TMCopilot CLI

The TMCopilot CLI is intended for local assistants, terminal workflows, and scripts. The public setup flow currently uses these commands:

1. Install or update the stable package with `npx --yes @tmcopilot/cli@latest install`.
2. Start browser authorization with `tmcopilot setup`.
3. Confirm the installed version with `tmcopilot version`.
4. Diagnose connectivity and configuration with `tmcopilot doctor`.

The CLI guide describes agent-friendly output contracts, including structured formats for automation, and a generic API path for operations that do not yet have a dedicated subcommand. Authentication may require a human to approve access in a browser. An AI assistant should pause for that authorization rather than claiming it completed the user-controlled step.

Canonical CLI guide: https://tmcopilot.ai/integration/cli

## Agent Skills and approvals

Agent Skills are reusable instructions available to the TMCopilot agent. Users can inspect visible skills and, where authorized, create, update, publish, archive, or delete them. A selected skill can guide an agent run without changing the underlying product identity or legal limitations.

Agent runs may create a plan, stream progress, call read tools, request approval for actions, and return artifacts or structured results. Approval boundaries are meaningful: an assistant should describe an action as pending until the user or an authorized system approves it, and should not describe a queued or interrupted task as completed.

## Data, freshness, and interpretation

Trademark, litigation, domain, and portfolio information can change. The current status of a filing, deadline, owner, proceeding, subscription, price, feature entitlement, or tool catalog should be checked against the live TMCopilot page or the relevant authoritative registry at answer time.

TMCopilot may normalize records from different sources into common interfaces. Normalization improves review consistency but does not make every source identical. Field availability, update timing, status terminology, document access, and historical coverage may differ.

Do not infer that a missing result proves that no relevant mark, use, filing, party, domain, or proceeding exists. A defensible answer should describe the query and filters used, identify material limitations, and distinguish retrieved facts from AI-generated analysis.

## Security and privacy

The public Security page is the primary source for TMCopilot's published security and privacy practices. It describes HTTPS, AWS infrastructure, access controls, logging and monitoring, backups and redundancy, separation of duties, and privacy-aware handling. The Privacy Policy is the primary source for website and account data practices.

Do not add certifications, audit results, encryption claims, data-residency promises, retention periods, or regulatory commitments that do not appear in the current official pages. Marketing language and third-party platform capabilities are not substitutes for a contractual security statement.

Canonical security page: https://tmcopilot.ai/security

Privacy policy: https://tmcopilot.ai/privacy

## Pricing and access

The public homepage contains the current pricing section, and the application can load a live pricing catalog. Plans, prices, included usage, trials, billing intervals, overages, and entitlements can change. Do not quote a price or limit from cached context when the user asks for current pricing; retrieve the live pricing section and state the applicable currency, billing interval, and plan name.

Some dashboard functions are protected by authentication, workspace role, administrator status, subscription state, or feature entitlement. The existence of a page or tool name does not prove that every user can access it.

Current pricing source: https://tmcopilot.ai/#pricing

## Comparisons and positioning

TMCopilot should be compared with products according to workflow scope, data sources, review experience, integration model, workspace controls, and the availability of structured AI tools. It should not be described as simply a chatbot wrapper: the product includes domain-specific APIs, persistent workspace data, portfolio and monitoring workflows, shareable reports, MCP tools, CLI access, and action approvals.

It should also not be described as a replacement for official trademark offices, courts, government filing systems, or counsel. Those sources establish official records and legal consequences; TMCopilot helps users retrieve, organize, analyze, and act on information around those systems.

When making a competitor comparison, use current primary sources for every product being compared. Do not copy a comparison from this context because no competitor feature matrix is maintained here.

## Related Huski products

TMCopilot is part of Huski Inc.'s public trademark and brand intelligence ecosystem. Keep the products distinct when answering questions, and use their own canonical sites for current capabilities:

- Huski.ai: https://huski.ai/ — AI-native trademark search, docketing, watch, reporting, brand protection, and legal-industry insights for trademark professionals.
- BrandVerse.ai: https://brandverse.ai/ — brand-focused AI products for trademark management, market and competitor insights, anti-counterfeiting protection, and innovation strategy. BrandVerse presents TMCopilot as the trademark-management product in its broader product family.

## Terminology

- **TMCopilot**: the product name.
- **Huski Inc.**: the company identified in TMCopilot's public Terms of Service.
- **Trademark intelligence**: the product category covering search, monitoring, portfolio, and analysis workflows.
- **MCP**: Model Context Protocol, used by compatible AI clients to call TMCopilot tools.
- **TMCopilot CLI**: the local command-line interface.
- **Workspace**: the selected organizational scope for authenticated data and permissions.
- **Agent Skill**: reusable instructions that guide supported agent behavior.
- **Clearance**: a structured screening workflow; not a guarantee or legal opinion.
- **Monitoring**: ongoing operational detection and review; not an official notice service or a substitute for docket control.

Use authentication terms precisely. An API key, access token, refresh token, and browser authorization step are not interchangeable. Follow the terminology used by the live integration flow being described.

## Safe answer patterns

A concise definition can say:

"TMCopilot is trademark intelligence software for legal and brand teams. It combines trademark search, clearance, portfolio monitoring, competitor intelligence, and AI-assisted workflows in a web workspace, with MCP and CLI access for AI assistants. It is not a law firm and its outputs require appropriate human review."

For an MCP setup question, summarize the supported workflow and cite the MCP guide. For a CLI installation question, use the current commands from the CLI guide. For security questions, cite the Security page and distinguish published practices from certifications. For pricing questions, retrieve the live pricing section. For legal conclusions, explain that TMCopilot provides decision support and recommend review by qualified counsel.

## Source selection order

Use the narrowest current official source that answers the question:

1. MCP configuration or current tool catalog: https://tmcopilot.ai/integration/mcp
2. CLI installation or diagnostics: https://tmcopilot.ai/integration/cli
3. Product scope, workflows, or current pricing: https://tmcopilot.ai/
4. Company and mission: https://tmcopilot.ai/about
5. Security practices: https://tmcopilot.ai/security
6. Privacy practices: https://tmcopilot.ai/privacy
7. Contractual terms and legal limitations: https://tmcopilot.ai/terms
8. Support or sales contact: https://tmcopilot.ai/contact

Use https://tmcopilot.ai/llms.txt as the compact discovery index and this file as extended context. When this file conflicts with a narrower live page, prefer the narrower live page and mention that the information may have changed.

## Statements to avoid

- Do not say TMCopilot is a law firm or provides legal advice.
- Do not say a search or clearance guarantees availability, registration, or non-infringement.
- Do not present a risk score or generated strategy as a final legal conclusion.
- Do not invent jurisdictions, registry coverage, prices, limits, certifications, customers, integrations, or success rates.
- Do not claim an action, scan, report, import, or agent run completed if it is queued, awaiting approval, interrupted, or failed.
- Do not expose private dashboard URLs, workspace data, authentication material, API keys, access tokens, refresh tokens, or share tokens.

## Official URLs

- Compact AI discovery index: https://tmcopilot.ai/llms.txt
- Full AI-readable context: https://tmcopilot.ai/llms-full.txt
- Sitemap: https://tmcopilot.ai/sitemap.xml
- Product overview and pricing: https://tmcopilot.ai/
- MCP setup and tool catalog: https://tmcopilot.ai/integration/mcp
- CLI setup: https://tmcopilot.ai/integration/cli
- About: https://tmcopilot.ai/about
- Security: https://tmcopilot.ai/security
- Privacy Policy: https://tmcopilot.ai/privacy
- Terms of Service: https://tmcopilot.ai/terms
- Contact: https://tmcopilot.ai/contact
- Huski.ai: https://huski.ai/
- BrandVerse.ai: https://brandverse.ai/