Publisher guide
Publish an MCP server
Register an existing MCP server with Seren to make its tools and resources discoverable through the publisher catalog, apply access policy, and receive usage-based payments. Use the CLI for this one-time registration, then use Seren MCP to inspect and operate the publisher.
Step 1
Expose a Streamable HTTP endpoint
The server must be reachable over HTTPS and support normal MCP initialization, tool discovery, and tool calls. Resources are optional but can also be discovered and read through Seren. Keep sampling and any server-specific extensions outside the required integration path.
Step 2
Register the MCP integration
Use the integration category, set integration_type to mcp, and provide the public endpoint. Static, JWT, and OAuth client-credentials upstream authentication are available when the MCP server is not public; passthrough authentication instead forwards each caller's own bearer token to the upstream MCP server.
seren agent create-publisher --organization-id <organization-id> --name "Analysis Tools" --slug analysis-tools --description "Dataset analysis tools and reports" --publisher-category integration --integration-type mcp --mcp-endpoint https://mcp.example.com/mcp --wallet-address <publisher-payment-destination> --wallet-network-id <publisher-payment-network-id>Run seren organizations first if you need the owning organization ID. When the upstream server requires authentication, add the matching CLI authentication flags; Seren encrypts stored credentials.
Step 3
Verify tool and resource discovery
After registration, list the publisher's MCP tools and resources through Seren. Check names, descriptions, input schemas, and response behavior. Tool names are case-sensitive, and the upstream server must remain available for discovery and calls.
List the MCP tools for the analysis-tools publisher.
Describe the analyze_data tool and its required arguments.
List the resources exposed by analysis-tools.Step 4
Price and protect calls
Configure pricing for each accepted asset, then review which tools can mutate upstream state. Use publisher endpoint policy and managed employee approval policy together: publisher policy controls what the integration exposes, while employee policy controls which exposed actions a particular employee may use.
Operate
Monitor availability and earnings
Track publisher revenue, daily revenue, top agents, earnings, and payout requests through the organization publisher API. Monitor the upstream MCP endpoint separately for transport errors, tool failures, latency, and authentication expiry.