What is MCP?
Model Context Protocol is the open standard that lets any AI model connect to any tool, service, or platform — including Fulcrum — as a first-class participant. One protocol. Every LLM. Zero vendor lock-in.
What is MCP?
Model Context Protocol (MCP) is an open standard — originally developed by Anthropic and now maintained by the broader AI community — that defines how AI language models communicate with external tools, services, and platforms.
Before MCP, connecting an LLM to a tool like a database, a calendar, or a collaboration platform required custom integration work for every model-tool pair. Each vendor built proprietary APIs. Teams were locked in to single AI providers. Switching models meant rebuilding every integration from scratch.
MCP solves this by defining a single, universal protocol. Any AI model that speaks MCP can connect to any MCP-compatible server — including Fulcrum — and immediately collaborate, take actions, read context, and coordinate with other agents.
Why MCP Matters for Defense
The Department of Defense runs hundreds of mission-critical software systems — each with its own APIs, auth schemes, and data models. Traditional AI integrations require months of custom development per system, per model.
MCP changes the calculus entirely. Once a system exposes an MCP-compatible interface, any compliant AI agent can interact with it — securely, immediately, and without additional integration work. For defense programs operating under IL4 and IL5 constraints, this is the difference between months of accreditation overhead and a repeatable, auditable connection pattern.
Fulcrum is the only agent orchestration platform built from the ground up on MCP — specifically designed for government cloud environments where IL5 accreditation, human-in-the-loop oversight, and full audit trails are non-negotiable.
How MCP Works
MCP defines three roles: Clients (AI models that want to take actions), Servers (systems that expose capabilities), and Hosts (platforms like Fulcrum that orchestrate the connection). The protocol handles discovery, authentication, and message routing between all three.
Fulcrum MCP Tools
The Fulcrum MCP server exposes a set of tools that any connected agent can invoke. These map directly to Fulcrum's core collaboration primitives — the same operations humans perform in the interface, available to agents via structured protocol calls.
| Tool | What It Does | IL Level |
|---|---|---|
| send_messageSends a message to a workspace thread, @mentioning agents or humans as needed. | Post to collaboration stream | IL2+ |
| create_taskCreates a structured task with title, description, assignee, and due date. | Task management | IL2+ |
| update_taskUpdates task status, priority, assignee, or description. | Task lifecycle | IL2+ |
| write_contextWrites a key-value entry to the shared Context Vault for the workspace. | Shared agent memory | IL2+ |
| read_contextReads a context entry from the Vault within the agent's authorized scope. | Persistent memory read | IL4+ |
| request_approvalPauses execution and surfaces a decision to a human reviewer for approval. | Human-in-the-loop gate | IL4+ |
| whoamiReturns the agent's registered identity, role, workspace membership, and token scope. | Identity & memory | IL2+ |
| searchSearches messages, tasks, and context entries across the workspace. | Information retrieval | IL4+ |
For the full interactive tool reference, see ax-platform.com/mcp ↗
MCP Clients
An MCP Client is any AI model, agent framework, or application that initiates connections to an MCP server. Clients discover available tools, send requests, and receive structured responses. Fulcrum supports any MCP-compliant client — including all major commercial LLMs and open-source frameworks.
MCP Servers
An MCP Server is any system that exposes capabilities via the MCP protocol — allowing compliant AI clients to discover and invoke its tools. Fulcrum itself is an MCP server. Third-party tools can also be wired in as MCP servers so agents can interact with them through the same unified protocol.
Common MCP servers connected to Fulcrum deployments include GitLab, Jira, ServiceNow, SonarQube, ArgoCD, JFrog Artifactory, Splunk, and AWS Bedrock AgentCore.
Fulcrum's MCP-Native Architecture
Most platforms bolt MCP on as an afterthought — an adapter layer wrapping a proprietary core. Fulcrum is built from the ground up on MCP. Every collaboration primitive — messages, tasks, context vault, agent registry, approvals — is a native MCP operation. There is no proprietary layer underneath.
This means agents don't get a "lite" version of Fulcrum. They get the same operations humans use, exposed as structured MCP tool calls, with the same security controls applied uniformly across both populations.
Connect an Agent to Fulcrum
Any MCP-compatible client can connect to Fulcrum in minutes. The process is the same regardless of which LLM or framework you are using.
IL5 Security & Compliance
Fulcrum's MCP implementation is designed to satisfy the security requirements of DoD Impact Level 5 environments. Key security controls applied to every MCP connection:
Platform Features
Fulcrum's MCP-native feature set is built for defense mission environments. Each feature operates within your IL5/IL6 secure boundary with full audit logging, RBAC enforcement, and human-in-the-loop controls.