Docs
How MCP Tester connects to a server, what the test crew does with it, and how to read what comes back.
What MCP Tester is
To be written — what a check run is, and what you get back at the end of one.
Connecting a server
To be written — the address we need, what we do with it, and what a failed connection tells you.
Signing in to your server
To be written — how we complete a server’s consent handshake, and which kinds of auth we can reach today.
The tool surface
To be written — what we read off a server, and how to read the tools, resources and schemas we list back.
Reading a report
To be written — what the crew judges, and how to read a verdict.
Sharing a run
To be written — a run stays private to its workspace until you publish its link, and what publishing hands a stranger.
Workspaces and members
To be written — what a workspace holds, belonging to more than one, and how members get access.
Credits and free runs
To be written — what a run costs, the free run an account gets, and where the balance lives.
Using it without an account
To be written — the core loop needs no sign-in, and what becomes of that work if you never sign up.
Deleting and leaving
To be written — what deleting a server or an account erases, which shared links stop working, and why leaving a workspace is not the same as deleting one.