FeaturesPublishingOverview

Publishing to Anypoint Exchange

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

What is Anypoint Exchange?

Anypoint Exchange is MuleSoft’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 MA²D

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

Prerequisites

Before publishing:

  1. Anypoint Platform Account: Free or paid account
  2. Connected Credentials: Configure in MA²D settings
  3. Compliance Score: Minimum 80% required
  4. Complete Documentation: All fields filled
  5. 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

  1. Navigate to your MCP Server or Agent Card
  2. Click “Publish to Exchange”
  3. 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:

  1. Go to Settings → Integrations
  2. Select Anypoint Platform
  3. Enter credentials:
    • Client ID: From Anypoint Platform
    • Client Secret: From Anypoint Platform
    • Organization ID: Your org ID

MA²D securely stores these credentials.

4. Publish

  1. Review publishing details
  2. Click “Publish Now”
  3. Wait for confirmation (30-60 seconds)
  4. 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

MA²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:

  1. Update your server/agent card
  2. Increment version number appropriately
  3. Add changelog entry
  4. 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

  1. Update your server/agent card in MA²D
  2. Test changes locally
  3. Increment version
  4. 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:

  1. Go to asset in MA²D
  2. Click “Manage in Exchange”
  3. 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

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:

OverviewOverview