Territory News MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| territory_auth_statusA | Check current authentication status for Territory News, including logged-in user email, user ID, and session file path. |
| territory_login_browserA | Launches a visible browser window for one-time Clerk authentication to Territory News. Captures the session cookie and saves it locally. |
| territory_logoutA | Clear saved session credentials from local storage. |
| territory_search_companiesB | Search for public and private companies on Territory News using fuzzy name matching. Returns name, domain, logo, and ticker. |
| territory_preview_signalsA | Preview recent real-time qualified news signals and headlines for a given company before adding it to your territory. |
| territory_get_tracked_companiesA | Get the list of currently monitored companies in your territory (supports up to 10 accounts). |
| territory_update_tracked_companiesA | Add, remove, or replace monitored companies in your territory (max 10 companies). Automatically resolves domains and tickers. |
| territory_get_seller_contextA | Get the seller's active sales context (Role, Account Segment, Selling Product, Primary/Secondary Use Cases, Value Proposition, and Enriched AI Context). |
| territory_set_seller_contextA | Configure or update your sales context (Role, Target Segment, Product Sold, Use Cases, Value Created). Automatically calls Territory News AI enrichment engine to tailor deal signals and conversation starters. |
| territory_get_signalsB | Get real-time news signals, executive inflection events, and tailored conversation openers for all tracked accounts in your territory (or for specific requested companies). |
| territory_trigger_scanB | Triggers a live re-scan of news and signal triggers across all monitored accounts in your territory. |
| territory_submit_feedbackA | Submit feedback on a signal, recommendation, or conversation starter to improve intelligence relevance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools map to distinct resources and actions: auth lifecycle, company search, tracked-company management, seller context, and signal retrieval are clearly separated. There is minor overlap between preview_signals and get_signals since get_signals can also target specific companies, though the intended pre-add versus tracked-account use case helps.
All tools share a consistent territory_ prefix and nearly all follow a verb_noun structure such as search_companies, get_tracked_companies, and set_seller_context. Small deviations like territory_auth_status and territory_login_browser weaken the verb-first pattern slightly, but the overall convention remains predictable.
12 tools is a well-scoped size for a territory intelligence MCP server, with separate groups for auth, company lookup, territory management, seller context, signals, and feedback. Each tool has a distinct responsibility and none feel redundant.
The surface covers the full workflow: authentication, company discovery, signal preview before adding, tracked-company management, seller context configuration, signal retrieval, live rescans, and feedback submission. There are no obvious dead ends or missing lifecycle operations.