MCP Server Documentation Overview

Understand the Model Context Protocol and how NeoArc Studio documents MCP servers. Learn about the three primitives (tools, resources, prompts), transport modes, authentication, and how MCP fits into your architecture documentation workflow.

February 26, 2026

The Model Context Protocol (MCP) is an open standard created by Anthropic that provides a uniform way for AI assistants to connect to external data sources and tools. Rather than building bespoke integrations for every system an AI agent needs to access, MCP defines a protocol layer that any server can implement and any client can consume.

NeoArc Studio treats MCP servers as a first-class integration type alongside REST APIs, GraphQL APIs, gRPC services, AsyncAPI event streams, and webhooks. Each MCP server gets a dedicated directory in the Integration Design section of your workspace, with structured JSON files for the server definition and each of its tools, resources, and prompts.

The Three Primitives

MCP organises server capabilities into three complementary primitive types. Each serves a distinct role in how AI assistants interact with external systems.

How MCP Fits Into Your Architecture

MCP servers sit at the boundary between your internal systems and AI agents. They expose a controlled surface area that determines what the AI can see and do.

Directory Structure

Each MCP server gets its own directory under Integration Design > MCP Servers. The directory contains a server definition file and subdirectories for each primitive type.

integration-design/mcp-servers/
  my-server/
    my-server.cf.mcp-server.json    # Server definition
    tools/
      search-data.cf.mcp-tool.json   # Tool definitions
      create-item.cf.mcp-tool.json
    resources/
      data-feed.cf.mcp-resource.json  # Resource definitions
    prompts/
      analyse.cf.mcp-prompt.json      # Prompt definitions

Publishing and Viewing

When you publish your documentation site, MCP servers appear in the viewer sidebar as a navigable tree grouped by primitive type. Each server shows its tools, resources, and prompts with detail viewers that render annotations, schemas, examples, and transport configuration.

Next Steps

Getting Started with MCP Server Documentation

Create your first MCP server documentation in NeoArc Studio. Walk through creating a server directory, configuring the server definition with transport and authentication, and adding tool, resource, and prompt definitions.

MCP Tools and Annotations

Deep dive into MCP tool definitions: annotation flags, safety matrix, input/output schemas, error scenarios, result content types, related resources, and example patterns. Learn how to document tools that AI assistants can use safely and effectively.

MCP Resources and URI Templates

Learn how to document MCP resources: concrete URIs, URI templates with parameters, content types, subscriptions, audience control, and metadata. Understand the difference between tools and resources and when to use each.