DemoSign In
ARCHAI CORE

Context lets the mission understand the enterprise.

Enterprise Context MCP is the Context layer of ARCHAI Core. It makes authorized enterprise information available to a mission, including capabilities, processes, applications, risks, controls, and owners, according to the sources and permissions agreed for each implementation. Studio organizes the mission; the MCP supplies permitted context; a person reviews the evidence and decides.

01Authorized sources
02Context for the mission
03Evidence for review

Available sources and connections depend on the implementation. This architecture explanation does not imply automatic access to an organization's systems.

See the full ARCHAI Core
ARCHAI ENTERPRISE CONTEXT MCP™

A search-only MCP server over seeded mission context

Enterprise Context MCP exposes a fixed catalog of pre-built enterprise missions and mission templates. Signed-in people and bearer-token AI agents get the exact same search tools over the exact same data — nobody creates, schedules, or runs anything through this product.

JSON-RPC 2.0 over HTTPBearer Token AuthAudited AccessRead-Only, No Writes
Quick StartExplore the tools

How it works

One seeded dataset, two front doors — a human dashboard and an MCP endpoint — both read-only and both logged.

1

Seeded catalog

  • ~10 mission templates
  • ~18 missions across 5 domains
  • Never created or edited through the UI
2

Two auth surfaces

  • Session cookie for the dashboard
  • Per-account bearer token for MCP
  • Same account, two credential types
3

One audit trail

  • Every dashboard search is logged
  • Every MCP tools/call is logged
  • Visible to admin & architect roles

Quick Start

Three steps take a seeded role account from sign-in to a live MCP tool call.

1

Sign in with a seeded role account

There are five seeded accounts — admin, architect, contributor, reviewer, viewer. All five search identical data.

Open Sign In
2

Copy your MCP API token

The dashboard shows a "Your MCP API token" card right after login. This bearer token is what an AI agent uses — never your password.

ecm_account.api_token
ecm_5a9320b0f26f91e8e8a1430ad7a4588d1e702ec632befe92
3

Call the MCP endpoint

Point your agent (or curl) at the endpoint below with a JSON-RPC 2.0 body.

curl
curl -X POST https://your-deployment.vercel.app/api/enterprise-context-mcp/mcp \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "tools/call",
    "params": {
      "name": "search_missions",
      "arguments": { "query": "governance" }
    }
  }'

Authentication

Human sessions and agent tokens are separate credentials issued to the same seeded account.

Dashboard login

  • Username and password
  • Sets an ecm_session cookie (7 days)
  • Passwords hashed with scrypt, never stored in plain text

MCP authentication

  • Long-lived per-account bearer token
  • Sent in the Authorization header
  • Identical search access for all 5 accounts
Header
Authorization: Bearer YOUR_API_TOKEN
Content-Type: application/json

MCP Endpoint

/api/enterprise-context-mcp/mcp
POSTJSON-RPC 2.0Bearer Token

Supported methods

resources/listtools/listtools/call

A GET request to the same path returns a plain-JSON description of the server and its tool names, useful as a health check.

Available MCP Resources

Two read-only resources describe the shape of the seeded catalog exposed through resources/list.

Missions

enterprise-context://missions
TitleStatusPriorityDomainDescriptionDeliverableTagsTemplate link
Sample record
{
  "id": "msn_8f2c1a",
  "templateId": "tpl_ai-governance-report",
  "templateName": "AI Governance Reporting",
  "title": "Regulatory Monitoring — AI Act Implementation Guidance",
  "status": "available",
  "priority": "high",
  "domain": "AI Governance",
  "description": "Track incoming regulatory guidance relevant to active AI systems.",
  "deliverable": "Board-ready compliance briefing",
  "tags": ["ai-governance", "iso-42001", "compliance"]
}

Mission Templates

enterprise-context://mission-templates
NameCategorySummaryDetailsTags
Sample record
{
  "id": "tpl_cmdb-discovery",
  "name": "CMDB Discovery & Reconciliation",
  "category": "Configuration Management",
  "summary": "Crawl enterprise systems to discover configuration items and reconcile them against the CMDB of record.",
  "tags": ["cmdb", "discovery", "itsm", "reconciliation"]
}

Available MCP Tools

Four tools — every one of them read-only. There is no create, update, or delete tool on this server.

Missions & templates

Missions and mission templates are pre-seeded reference content. Nobody — human or agent — creates, schedules, or runs one through this product; the point of searching is to retrieve context that already exists.

Mission template

A reusable definition — name, category, summary, details, tags. About 10 seeded templates span categories like Configuration Management, AI Governance, Enterprise Architecture, Market Intelligence, and Portfolio Management.

Mission

A concrete instance of a template — title, status, priority, domain, description, deliverable, tags. About 18 seeded missions carry status (available, in progress, completed, archived) and priority (low to critical) as informational fields an agent can filter by.

Seeded roles

Five roles, identical search access. The only role-gated surface is the audit log page.

RoleExample accountSearch missions & templatesView audit log
adminElena Voss, Admin
architectMarcus Chen, Enterprise Architect
contributorPriya Nair, Contributor—
reviewerSofia Delgado, Reviewer—
viewerTom Okafor, Viewer—

Audit trail

Every search and login — from the dashboard or from an MCP agent — writes one row, so usage is traceable per account.

ActorActionQueryResultSource (dashboard | mcp)When

Visit the audit log page while signed in as admin or architect to see recent dashboard and MCP activity side by side, each row tagged with its source.

Troubleshooting

401 Unauthorized

  • Missing Authorization header
  • Token does not match any seeded account
  • Token copied with extra whitespace

Sign in to the dashboard and copy the token from the "Your MCP API token" card again.

-32602 Unknown tool

  • The "name" field in tools/call does not match one of the four tool names exactly.

Call tools/list first to confirm the exact tool names available on this server.

Empty search result

  • No seeded mission or template matches the given filters.

Broaden the query or drop a filter — the catalog is a fixed, pre-seeded set, not a live index.

-32700 Parse error

  • The request body was not valid JSON.

Send a JSON-RPC 2.0 body with method, params, and Content-Type: application/json.

Frequently Asked Questions