Add doc for testing FastMCP servers with postman

[strawgate]

Enhancement

https://learning.postman.com/docs/postman-ai/mcp-requests/overview

[marvin-context-protocol]

Claude finished @strawgate's task in 2m 15s —— View job

---

Recommendation

Add a new section to docs/patterns/testing.mdx documenting how to test FastMCP servers using Postman's MCP request feature. This should be added alongside the existing pytest-focused testing documentation.

Findings

Current Testing Documentation

FastMCP has two main testing documentation files:

1. docs/patterns/testing.mdx - User-facing guide focused on testing MCP servers with pytest and the FastMCP Client. This is where Postman documentation should be added.

2. docs/development/tests.mdx - Internal development guide for contributors writing tests for FastMCP itself.

The HTTP deployment documentation (docs/deployment/http.mdx:157) mentions MCP Inspector as a browser-based testing tool, establishing precedent for documenting external testing tools.

Postman MCP Capabilities

According to Postman's documentation (https://learning.postman.com/docs/postman-ai/mcp-requests/overview), Postman now supports:

• Making MCP requests to MCP servers
• Testing MCP tools, resources, and prompts
• Debugging MCP server responses
• Similar to MCP Inspector but within the Postman environment

This makes Postman a viable alternative testing tool, especially for teams already using Postman for API testing.

Where Documentation Should Go

The new Postman testing section should be added to docs/patterns/testing.mdx for these reasons:

1. Existing structure: The file already covers testing FastMCP servers and is in the "Deployment" section of docs navigation alongside other operational guides
2. User-facing: Postman is a user/developer tool, not an internal FastMCP development tool
3. Precedent: The HTTP deployment docs already mention MCP Inspector as a testing tool (line 157)
4. Logical flow: Developers reading about testing will find both pytest (programmatic) and Postman (interactive) options in one place

Detailed Action Plan

A junior developer implementing this enhancement should:

1. Add new section to docs/patterns/testing.mdx after the existing pytest content (around line 104):

   • Section title: "## Testing with Postman" or "## Interactive Testing with Postman"
   • Brief introduction explaining Postman's MCP support
   • Prerequisites: Running FastMCP server over HTTP (link to HTTP deployment docs)
   • Step-by-step guide:
     • Deploy server with HTTP transport (reference existing HTTP docs)
     • Configure Postman to connect to the MCP server
     • Test tools/resources/prompts via Postman UI
     • Debug responses and view request/response details
   • Link to Postman's documentation for detailed MCP request features
   • Note about when to use Postman vs pytest (interactive exploration/debugging vs automated testing)
   • Follow the existing documentation style (see CLAUDE.md guidelines)

2. Add cross-reference in docs/deployment/http.mdx:

   • Add Postman to the list of browser-based MCP clients alongside MCP Inspector (around line 157)
   • Update the bullet list to include: "Postman - API testing platform with MCP request support"
   • Link to the patterns/testing.mdx page for full documentation

3. Verify docs.json navigation (already included):

   • File is already in navigation at line 214: "patterns/testing"
   • No changes needed to navigation structure

4. Test the documentation:

   • Run just docs or mintlify dev to preview locally
   • Verify links work correctly
   • Ensure code examples are properly formatted
   • Check that navigation flows logically

Related Files

Repository	File	Relevance	Sections
jlowin/fastmcp	docs/patterns/testing.mdx	Primary file where Postman testing documentation should be added	After line 104
jlowin/fastmcp	docs/deployment/http.mdx	Should add cross-reference to Postman alongside MCP Inspector	Line 157
jlowin/fastmcp	docs/docs.json	Mintlify navigation config (already includes testing.mdx)	Line 214
jlowin/fastmcp	CLAUDE.md	Contains documentation guidelines that must be followed	Documentation Guidelines section

Related Webpages

Name	URL	Relevance
Postman MCP Requests Overview	https://learning.postman.com/docs/postman-ai/mcp-requests/overview	Official Postman documentation for MCP testing capabilities referenced in the issue

---

Investigation complete. This issue requests documentation for a new testing tool (Postman) that now supports MCP. The recommendation is to add a dedicated section to the existing testing documentation, following the precedent set by the MCP Inspector documentation. No related issues or pull requests found addressing this specific enhancement.

[strawgate]

/marvin make it happen

[marvin-context-protocol]

Claude finished @strawgate's task in 1m 47s —— View job • claude/issue-3091-20260206-0232 • Create PR ➔

---

Task: Add Postman Testing Documentation ✅

Successfully added documentation for testing FastMCP servers with Postman's MCP request feature.

Tasks

• Read existing documentation files to understand structure and style
• Add new "Testing with Postman" section to docs/patterns/testing.mdx
• Add cross-reference to Postman in docs/deployment/http.mdx
• Run linting and formatting checks
• Commit and push changes
• Provide PR creation link

Changes Made

Added comprehensive Postman testing documentation to the FastMCP docs:

1. New section in docs/patterns/testing.mdx: Added "Testing with Postman" section covering:

   • Prerequisites for testing with Postman
   • Setup instructions for deploying a FastMCP server over HTTP
   • Overview of Postman's MCP capabilities (listing tools/resources/prompts, calling tools, reading resources, executing prompts, debugging)
   • Link to official Postman MCP documentation
   • Guidance on when to use Postman vs Pytest (interactive exploration vs automated testing)

2. Cross-reference in docs/deployment/http.mdx: Added Postman to the list of browser-based MCP clients that need CORS configuration, with a link to the new testing documentation.

The documentation follows the established style guidelines from CLAUDE.md, with prose explanations before code examples and user-focused content.

--- •