Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add Postman to community servers #482

Conversation

shannonlal
Copy link
Contributor

@shannonlal shannonlal commented Jan 5, 2025

Adding Postman server to the community servers list.

Description

Adding Postman to the community servers list in README.md. This server provides Postman API testing through the Newman runner.

Server Details

  • Server: Postman
  • Changes to: README.md (adding new community server)

Motivation and Context

Postman is a popular API Testing framework that allows for quick testing and validation of APIs for developers. Under the hood it combines Postman and Newman (A Postman collection runner) that enables developers to build collections and then use for integration testing. Adding it to the community servers list will help users discover and utilize Postman functionality in their API Development. The server provides:

  • The ability to run Postman collections
  • The ability to get the test results back from these collections
  • Can create and update Postman Colletions

How Has This Been Tested?

Tested with Claude in Cline (VS Code):

  • Create Postman Collections
  • Run the Postman Collections
  • Verify the responses from the collections with newman

Breaking Changes

No breaking changes. This is an additive change to the README.md only.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

The Postman server is available at: https://github.com/shannonlal/mcp-postman
It includes:

  • Complete documentation
  • MIT License
  • Contribution guidelines

Copy link
Member

@jspahrsummers jspahrsummers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! I'm Claude, and I'm reviewing PRs that add links to the README. This PR correctly adds Postman to the community servers section. Approving!

Copy link
Member

@jspahrsummers jspahrsummers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You've changed a bunch of other lines, which introduces merge conflicts. Can you please scope this PR to just the new server bullet?

@shannonlal shannonlal force-pushed the feat/add-postman-newman-server branch from ba97052 to 2a65f6d Compare January 10, 2025 13:36
@shannonlal shannonlal force-pushed the feat/add-postman-newman-server branch from 2a65f6d to c09bc43 Compare January 10, 2025 13:41
@shannonlal
Copy link
Contributor Author

@jspahrsummers I just fixed the merge conflicts for this PR. Let me know if there are any other changes required

Copy link
Member

@jspahrsummers jspahrsummers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see the diff for this PR—the changes are now even more substantial. I suggest running git merge main.

@shannonlal
Copy link
Contributor Author

@jspahrsummers ok. I had done a rebase and accept the changes. I will try a merge instead see if that works

@shannonlal
Copy link
Contributor Author

@jspahrsummers I think I will close this PR and open a new one and do a merge it will be eaiser

@shannonlal
Copy link
Contributor Author

@jspahrsummers I am closing this one and just opening a new one as I rebased instead of merged

@shannonlal shannonlal closed this Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants