thinkneo-control-plane
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THINKNEO_API_KEY | No | Your ThinkNEO API key used for Bearer token authentication. Required for protected tools such as spend tracking, guardrail evaluation, and policy enforcement. | |
| THINKNEO_MCP_API_KEYS | No | Used in self-hosted deployments to configure the allowed API keys for the server. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| thinkneo_check_spendB | Check AI spend summary for a workspace, team, or project. Returns cost breakdown by provider, model, and time period. Requires authentication. |
| thinkneo_evaluate_guardrailA | Evaluate a prompt or text against ThinkNEO guardrail policies before sending it to an AI provider. Returns risk assessment, violations found, and recommendations. Requires authentication. |
| thinkneo_check_policyB | Check if a specific model, provider, or action is allowed by the governance policies configured for a workspace. Requires authentication. |
| thinkneo_get_budget_statusB | Get current budget utilization and enforcement status for a workspace. Shows spend vs limit, alert thresholds, and projected overage. Requires authentication. |
| thinkneo_list_alertsA | List active alerts and incidents for a workspace. Includes budget alerts, policy violations, guardrail triggers, and provider issues. Requires authentication. |
| thinkneo_get_compliance_statusA | Get compliance and audit readiness status for a workspace. Shows governance score, pending actions, and compliance gaps. Requires authentication. |
| thinkneo_provider_statusA | Get real-time health and performance status of AI providers routed through the ThinkNEO gateway. Shows latency, error rates, and availability. No authentication required. |
| thinkneo_schedule_demoA | Schedule a demo or discovery call with the ThinkNEO team. Collects contact information and preferences. No authentication required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| thinkneo_governance_audit | Run a full governance audit for a workspace: check budget status, list active alerts, and review compliance readiness. |
| thinkneo_policy_preflight | Pre-flight check before switching to a new AI model or provider: verify it's allowed by workspace policy and evaluate guardrail compliance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ThinkNEO Getting Started | Quick-start guide for connecting your AI applications to the ThinkNEO control plane. |
| Supported AI Providers | List of AI providers supported by the ThinkNEO gateway with available models. |
TDQS
Scored across 8 tools
Tools are generally distinct with clear domains: policy (permissions), guardrail (content safety), spend (analytics), budget (limits), compliance (audit), alerts (incidents), and provider health. Minor semantic overlap exists between check_spend and get_budget_status (both financial), and between check_policy and evaluate_guardrail (both validation), but descriptions clarify their distinct scopes.
Consistent snake_case prefixing (thinkneo_) and mostly verb_noun structure (check, evaluate, get, list, schedule). Minor deviation with provider_status which lacks a verb prefix, breaking the pattern established by get_budget_status and get_compliance_status. Verbs vary (check/evaluate/get) but remain readable.
Eight tools is a reasonable count for an AI governance control plane, covering policy, cost, compliance, and operational monitoring. The inclusion of schedule_demo (a sales/marketing function) is slightly incongruous with the operational focus of the other seven tools, but doesn't bloat the set.
Strong observability coverage (read-only status checks, spend analysis, alert listing) but lacks expected control plane capabilities: no tools to create/update policies, set budgets, configure guardrails, or manage/acknowledge alerts. The surface is adequate for monitoring but incomplete for 'control' operations implied by the server name.