Verify and troubleshoot setup | Simplified Developer Docs

What a complete setup looks like

Check	Evidence
Connection	Simplified tools are available in the intended client/session
Authentication	`api_getWorkspaceInfo` returns the expected user and workspace
Teamspace	`api_listTeamspaces` resolves the intended destination
Skills, when installed	The client can discover the installed Simplified instructions

A configuration file or installer success message is not sufficient evidence of all four.

Run a read-only check

Ask your assistant:

Verify my Simplified setup. Use the tools to identify my workspace and list teamspaces. Check whether Simplified skills are available. Report each result separately, without creating content or spending credits.

Tool names may carry a client-specific prefix. If the current session has not loaded a newly installed server or skill, start a new session and run the check there.

Resolve the common failures

Symptom	Next step
No tools	Check server enablement, configuration scope, authentication, and session reload
Authentication required	Reconnect the affected Simplified entry and complete the supported sign-in flow
Unexpected workspace	Inspect which account or API key authenticated the connection
Missing teamspace	Check membership and credential scope; do not substitute another team’s ID
Skills but no tools	Complete MCP setup; installing instructions does not authenticate a server
Tools but no skills	Install skills where supported, or use the workflow guides directly
Missing capability	Check the connection’s tool inventory and client action permissions

Keep useful error messages, but remove credentials and signed URLs before sharing diagnostics. Change only the affected configuration; avoid broad deletion of client settings or authentication caches.

Instructions for an assistant performing setup

Identify the current platform and use its dedicated guide.
Inspect existing tools and skills before installing anything. Reuse working connections and follow the host’s permission policies.
Configure only the requested client and scope. A hosted sandbox is not the user’s computer.
Let the user complete sign-in through the supported client flow. Keep secrets out of chat and logs.
Reload or request a new session when necessary; do not claim live verification before tools are available.
Verify with read-only workspace and teamspace calls. Do not generate, publish, or create resources as a setup test.
Report the client, workspace, selected teamspace, skill availability, and any remaining action separately.

Continue with real work

Use the MCP quickstart for a first draft, or Explore Simplified to choose a capability. Install the CLI only if you also want terminal commands; it is optional for a hosted MCP connection.