AI Agents with MCP

Chapter 7. Testing, Securing, and Sharing Your MCP Server

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 7th chapter of the final book. Supplemental material (code examples, exercises, etc.) is available for download at https://github.com/kylestratis/ai_agents_mcp_examples

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

You’ve built your server. It provides tool, prompts, and resources to client applications. It supports a bevy of client-provided capabilities like sampling, elicitations, and roots, along with utilities to make your life and your users’ lives easier, like logging, notifications, and pagination. What’s next? Your work is not yet done. Like any other software project, you still need to test your server code, evaluate its performance, secure it, and finally share it with the world.

Testing should be familiar to the software engineer. Servers are code, after all, and thus testing them takes the same form as testing any other code: unit testing, integration testing, and end-to-end testing still take the spotlight here. But on top of that, you have additional tools, such as MCP Inspector (which we’ve been using throughout the server chapters) which allows you to directly ...