Client setup
Claude Code
Register a local stdio server and verify the tools inside Claude Code.
Use this guide for Claude Code, the terminal client. Claude Desktop uses a different configuration path and is covered separately. Toolport is shown as a local stdio process, so Claude Code starts the command when it connects.
Register a local server
claude mcp add --transport stdio toolport -- npx -y @toolport/mcp
Replace the package with your verified distribution before running it. The separator -- keeps server arguments distinct from Claude Code arguments. Choose the configuration scope deliberately; a project-scoped entry may be shared with your repository, so keep credentials out of it.
Provide the credential
TOOLPORT_TOKEN is the token variable used in this template contract. Pass it through a supported local secret or environment configuration for your client. Do not type the token into the conversation or commit it to .mcp.json. Registering the command alone does not supply authentication.
Verify in the client
Open the MCP status/tool view in Claude Code.
Confirm the toolport server connects without a startup error.
Confirm the four advertised tool names appear.
Ask for open bugs in one authorized repository and review the proposed arguments.
If discovery fails
Run the startup diagnostics first: can the client find npx, and does the verified package launch? A desktop or editor process may have a different PATH than your terminal. Check the server log after removing tokens and private issue text. Reload the server after changing configuration.
Remove the entry
claude mcp remove toolport
Removing an entry prevents future calls from this client. Revoke the tracker credential separately if it should no longer authorize access.