MCP requests

Choose Add MCP server in a collection or a section.

Connect

Codestamp supports two transports:

• STDIO: a command such as npx -y ..., started without a shell.
• Streamable HTTP: a URL.

Both take headers or environment variables. You can paste an mcpServers configuration from another client.

Use tools, prompts and resources

After Codestamp connects, it lists the server’s tools, prompts and resources. Pick one and fill in its arguments as JSON. Codestamp builds a template from the schema, and {{variable}} is filled in when you run it. Then use Run tool, Get prompt or Read resource.

Results appear in a readable form or as JSON, and the Messages tab shows every JSON-RPC message.

An MCP request is saved in the collection with the tool you picked. You can duplicate it, and it syncs with your team. Run all and the Postman export skip it, with a note.

Approval for STDIO

Before it runs a STDIO server, Codestamp asks you to approve the exact program, arguments and environment, after variables are filled in. It stores only their SHA-256 hash. Any change asks again, including a change that came from a teammate’s sync or a variable they edited.

The interface may call only the MCP methods on a whitelist (list, call, get, read, ping). Codestamp rejects requests from the server other than ping, and limits a message to 16 MB. STDIO programs stop with their session.