MCP Servers

Create, manage, and publish Model Context Protocol servers with MA²D’s no-code tools.

Overview

MCP Servers in MA²D provide three key components:

• Tools - Functions that AI agents can execute
• Resources - Data sources agents can access
• Prompts - Interaction templates for consistent behavior

Three Ways to Create Servers

1. Import from URL

Connect to existing HTTP-Streamable MCP endpoints:

• Automatic introspection of remote servers
• One-click import of tools, resources, and prompts
• Synchronization capabilities
• Extend with additional components

Best for: Integrating existing MCP servers

Learn more →

2. Import from OpenAPI

Convert REST APIs to MCP servers:

• Upload or paste OpenAPI 3.x specifications
• Automatic endpoint-to-tool conversion
• Request/response schema mapping
• Multiple specs per server

Best for: Wrapping REST APIs as MCP servers

Learn more →

3. Create from Scratch

Build custom mock servers:

• No-code tool schema builder
• Visual resource configuration
• Prompt argument builder
• Complete mock scenario support

Best for: Prototyping and testing

Learn more →

Key Features

Tool Management

• JSON schema builder for inputs/outputs
• Enable/disable individual tools
• Mock scenario configuration
• Real-time validation

Managing Tools →

Resource Management

• Resource templates and URIs
• Mock content configuration
• MIME type support
• Versioning

Managing Resources →

Prompt Management

• Argument definition
• Template configuration
• Example interactions
• Variable substitution

Managing Prompts →

Mock Scenarios

Create realistic test responses:

• Conditional matching
• Multiple scenarios per tool
• JSON response configuration
• Test before publishing

Mock Scenarios →

Live MCP Endpoints

Every server gets a live endpoint:

• HTTP-Streamable transport
• JSON-RPC 2.0 protocol
• Real-time testing
• Ready for AI agents

MCP Endpoints →

Authentication

Secure your MCP endpoints:

• Bearer token authentication
• Basic authentication
• OAuth2 client credentials
• Auto-generated credentials

Authentication →

Server Lifecycle

Quick Actions

Create Your First Server

1. Navigate to MCP Servers
2. Click "+ Add MCP Design Spec"
3. Choose creation method
4. Configure server details
5. Add tools/resources/prompts
6. Test the endpoint
7. Publish to Exchange

Quick Start Guide →

Common Operations

• Download Spec: Get JSON specification file
• Copy Endpoint: Copy MCP endpoint URL to clipboard
• Enable/Disable: Toggle components on/off
• Edit Metadata: Update server name, description, version
• Delete: Remove server and all components

Best Practices

Naming Conventions

• Server Names: Use descriptive, kebab-case names (weather-api-server)
• Tool Names: Clear action verbs (get_weather, search_products)
• Resource URIs: Follow REST patterns (weather://cities/SF)

Documentation

• Write clear, detailed descriptions (200+ characters)
• Provide examples for each tool
• Document expected inputs and outputs
• Include error scenarios in mocks

Testing

• Create multiple mock scenarios per tool
• Test with real MCP clients (Postman, Claude Desktop)
• Verify error handling
• Check compliance before publishing

Versioning

• Use semantic versioning (1.0.0, 1.1.0, 2.0.0)
• Document changes in descriptions
• Test backwards compatibility
• Coordinate with consumers

Server Status

Servers can have different statuses:

• Draft - Work in progress, not published
• Published - Available in Anypoint Exchange
• Archived - Deprecated but preserved

Compliance Checking

MA²D validates servers against design rules:

• Description length requirements
• Tool naming standards
• Mock scenario completeness
• Provider information

Learn about Design Rules →

Integration with Anypoint Exchange

Publish servers directly to Exchange:

• OAuth2 and Basic Auth support
• Asset metadata configuration
• Status tracking
• Version management

Publishing Guide →

MCP Protocol Compliance

MA²D implements MCP specification:

• HTTP-Streamable transport
• JSON-RPC 2.0 messaging
• Capability negotiation
• Standard error codes

MCP Protocol Details →

Example: Weather API Server

Here’s a complete example of an MCP server:

Server: weather-api-server

Tools:

• get_current_weather - Get current conditions
• get_forecast - Get 7-day forecast
• search_cities - Find cities by name

Resources:

• weather://cities - List of available cities
• weather://alerts - Active weather alerts

Prompts:

• weather_query - Template for asking about weather

View full example →

Next Steps

• Creating Servers - Detailed creation guide
• Managing Tools - Tool configuration
• Mock Scenarios - Testing strategies
• Publishing - Publish to Anypoint Exchange

Need Help? See Troubleshooting or check the FAQ.