Publishing to Anypoint Exchange

Share your MCP servers and Agent Cards with the world via Anypoint Exchange.

What is Anypoint Exchange?

Anypoint Exchange is Integration/API management’s marketplace for APIs, connectors, templates, and now MCP servers and Agent Cards. It provides:

Discovery: Users can find your assets
Documentation: Automatic documentation generation
Version Management: Maintain multiple versions
Access Control: Public or private sharing
Analytics: Track usage and downloads

Publishing from A²D

A²D integrates directly with Anypoint Exchange for one-click publishing.

Prerequisites

Before publishing:

Anypoint Platform Account: Free or paid account
Connected Credentials: Configure in A²D settings
Compliance Score: Minimum 80% required
Complete Documentation: All fields filled
Tested: MCP endpoint verified working

Publishing Steps

1. Prepare Your Asset

Ensure your MCP server or Agent Card is ready:

✅ Name: Clear, descriptive name
✅ Description: Comprehensive (200+ chars)
✅ Version: Semantic versioning (e.g., 1.0.0)
✅ Compliance: Score > 80%
✅ Testing: Endpoint working
✅ Documentation: Complete

2. Configure Exchange Settings

Navigate to your MCP Server or Agent Card
Click “Publish to Exchange”
Fill in Exchange details:

Asset Name: Weather API
Asset ID: weather-api
Group ID: your-org-id
Version: 1.0.0
Visibility: Public or Private
Categories: APIs, Weather, Data
Tags: weather, mcp, ai-agents

3. Configure Anypoint Credentials

First time publishing:

Go to Settings → Integrations
Select Anypoint Platform
Enter credentials:
- Client ID: From Anypoint Platform
- Client Secret: From Anypoint Platform
- Organization ID: Your org ID

A²D securely stores these credentials.

4. Publish

Review publishing details
Click “Publish Now”
Wait for confirmation (30-60 seconds)
View in Anypoint Exchange

What Gets Published

MCP Servers

When you publish an MCP server, Exchange includes:

OpenAPI Specification: Auto-generated from your MCP tools
MCP Endpoint URL: Live endpoint URL
Documentation: Tool descriptions, schemas, examples
Version Info: Current version and changelog
Mock Scenarios: Testing examples

Agent Cards

When you publish an Agent Card, Exchange includes:

A2A Specification: JSON agent card spec
Skill Definitions: All agent capabilities
MCP Server References: Links to underlying servers
Invocation Examples: How to use the agent
Compatibility Info: Supported frameworks

Publishing Workflow

Versioning

A²D follows semantic versioning:

Version Format

MAJOR.MINOR.PATCH (e.g., 1.2.3)

MAJOR: Breaking changes (1.0.0 → 2.0.0)
MINOR: New features, backward compatible (1.0.0 → 1.1.0)
PATCH: Bug fixes (1.0.0 → 1.0.1)

Publishing New Versions

To publish a new version:

Update your server/agent card
Increment version number appropriately
Add changelog entry
Republish to Exchange

Exchange maintains version history automatically.

Visibility Options

Public

✅ Discoverable by anyone
✅ Anyone can use
✅ Appears in Exchange search
✅ Good for open-source projects

Private

✅ Only your organization can see
✅ Requires authentication to use
✅ Hidden from public search
✅ Good for internal tools

Organization

✅ Shared within your org
✅ Multiple business groups
✅ Controlled access
✅ Good for enterprise

Exchange Asset Page

Once published, your asset gets a dedicated page with:

Automatic Documentation

Exchange generates:

API reference from schemas
Code examples in multiple languages
Interactive API console
Visual diagrams

Asset Details

Users can see:

Description and use cases
Version history
Dependencies
Technical specifications

Usage Analytics

Track:

Page views
Downloads
API calls
User feedback

Updating Published Assets

Making Changes

Update your server/agent card in A²D
Test changes locally
Increment version
Republish to Exchange

Best Practices

Test first: Always test before republishing
Version appropriately: Follow semantic versioning
Document changes: Add changelog entries
Notify users: For breaking changes
Deprecate gracefully: Give notice before removing

Unpublishing

To remove an asset from Exchange:

Go to asset in A²D
Click “Manage in Exchange”
In Exchange, click “Deprecate” or “Delete”

Note: Unpublishing may break existing integrations. Deprecate with notice instead when possible.

Exchange Categories

Organize your assets with categories:

For MCP Servers:

APIs
Data Services
AI/ML
Integration
Utilities

For Agent Cards:

Agents
AI Assistants
Automation
Customer Service
Analytics

Best Practices

Before Publishing

✅ Test thoroughly with real agents
✅ Achieve 90%+ compliance score
✅ Write comprehensive descriptions
✅ Add multiple mock scenarios
✅ Include usage examples
✅ Document error cases

During Publishing

✅ Choose appropriate visibility
✅ Add relevant tags
✅ Select correct categories
✅ Provide changelog
✅ Review final preview

After Publishing

✅ Monitor analytics
✅ Respond to user feedback
✅ Update documentation
✅ Maintain versioning
✅ Fix reported issues

Integration Examples

Using Published MCP Server

Once published, users can access your server:

import { Client } from '@modelcontextprotocol/sdk/client/index.js'
 
// Use your published MCP endpoint
const client = new Client({
  name: 'my-client',
  version: '1.0.0'
}, {
  capabilities: {}
})
 
await client.connect({
  url: 'https://ma2d.vercel.app/api/platform/YOUR_SERVER_ID/mcp'
})
 
// Use the tools
const result = await client.callTool({
  name: 'get_weather',
  arguments: { city: 'San Francisco' }
})

Using Published Agent Card

// Reference agent card from Exchange
{
  "agent": "your-org/weather-assistant",
  "version": "1.0.0",
  "invocation": {
    "skill": "get_weather",
    "arguments": {
      "location": "San Francisco"
    }
  }
}

Troubleshooting Publishing

”Compliance score too low”

Minimum 80% required
Fix issues shown in compliance report
Recheck and try again

”Invalid credentials”

Verify Anypoint Platform credentials
Check organization ID is correct
Ensure Connected App has permissions

”Asset already exists”

Asset name must be unique in your org
Use different name or delete old version
Check asset ID doesn’t conflict

”Version conflict”

Version must be higher than existing
Can’t republish same version
Increment version number

Next Steps

MCP Servers - Create servers to publish
Agent Cards - Design agent cards
Design Rules - Ensure compliance
Getting Started - Set up A²D

Ready to share your work? Follow the steps above to publish to Anypoint Exchange and make your MCP servers and Agent Cards discoverable by the world!

Learn More:

Anypoint Exchange Documentation
API Reference - Technical details

Overview Overview