MCP Server Documentation
Document Model Context Protocol (MCP) servers with structured tool definitions, resource catalogues, prompt templates, transport configuration, OAuth 2.1 authentication, and capability declarations. A purpose-built editor covers the three MCP primitives that AI-powered applications depend on.
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external data sources and tools. It defines three primitives - tools, resources, and prompts - that give LLMs structured access to systems they would otherwise have no visibility into. The dedicated MCP documentation workflow that captures server capabilities, transport configuration, authentication, and all three primitive types in a structured, publishable format stored in your Git repository alongside REST APIs, schemas, and architecture documentation.
The Three MCP Primitives
MCP organises server capabilities into three complementary primitive types, each serving a distinct role in how AI assistants interact with external systems.
Tool Documentation
Tools are the most common MCP primitive. NeoArc captures everything an LLM and a developer need to understand a tool's behaviour, safety characteristics, and integration requirements.
Tool Annotation Safety Matrix
NeoArc renders tool annotations as a semantic safety badge, helping both developers and LLMs understand the risk profile of each tool at a glance.
Resource Documentation
Resources expose data to AI assistants without requiring tool calls. They support both concrete URIs for fixed data and URI templates for parameterised access.
Prompt Documentation
Prompts are reusable templates that standardise how AI assistants interact with specific domains. They define arguments, expected message flows, and concrete examples.
Server Configuration
MCP servers require transport, authentication, and capability documentation that goes beyond the primitives themselves.
Import and Export
NeoArc supports importing and exporting MCP server definitions in standard formats for interoperability with the broader MCP ecosystem.
Example: E-Commerce AI Assistant
A complete MCP server definition for an e-commerce platform demonstrating all three primitives, transport configuration, and OAuth authentication.
Tools
Three tools demonstrating different annotation profiles: a read-only search, a read-only status query, and a non-idempotent write operation.
Resources
A templated resource for browsing the product catalogue and a static resource for the return policy.
Prompts
Two prompt templates: one for generating customer service responses with tone adaptation, and one for personalised product recommendations.
Viewer Experience
The published site includes an MCP server browser that presents all three primitives in a navigable hierarchy with dedicated detail viewers for each entity type.
Use Cases
Related Documentation
Document REST APIs with full endpoint specifications, OpenAPI import and export, seven HTTP methods, parameters, request and response bodies linked to shared schemas, authentication schemes, and a published API browser. REST is one of six API types (REST, GraphQL, gRPC, AsyncAPI, Webhooks, MCP) sharing a unified schema layer.
Document webhook-based integrations with event definitions, HMAC signature verification, delivery guarantees, retry policies, dead letter queues, circuit breakers, and consumer guidance. The structured webhook editor captures what architects need to express about push-based event notifications.
Document event-driven and asynchronous APIs with channels, operations, messages, protocol bindings for 18 protocols, 13 security schemes, reusable traits, and AsyncAPI 3.0 export in NeoArc Studio.
Document gRPC APIs with services, methods, four streaming types, proto message definitions, 17 status codes, 10 error detail types, interceptor chains, retry and hedging policies, HTTP transcoding, proto import and export, and a published gRPC API browser with streaming flow diagrams.
Define data structures with ten field types, 65+ type specialisations, and 50+ validation rules. Create reusable schemas that stay synchronised across your documentation.