Adding other servers
Woodentable can use other MCP servers on your agent's behalf: a browser, an image service, your own company's tools. Add a server once and every run can reach it.
Add a server
A server that runs as a program on your machine:
woodentable mcp add playwright -- npx @playwright/mcp@latest
A server at a web address:
woodentable mcp add docs https://example.com/mcp
Woodentable connects to the server when you add it, and keeps nothing if that fails, so a mistyped command shows up now rather than at your agent's first call.
Servers that ask you to sign in
woodentable mcp add comfy -oauth https://cloud.comfy.org/mcp
-oauth opens your browser at the service's sign-in page. What it gets back is kept in a file of its own that only you can read, never in the settings file, and renewed as it expires. If you're ever signed out, woodentable mcp login comfy signs you in again.
How your agent uses them
Your agent doesn't get a separate tool for every one of a server's tools. It calls them by name from its tcl_workspace script, as playwright::browser_navigate, so a server with forty tools costs it one tool's worth of attention, not forty. Resources and prompts a server offers are passed on to your agent's app as they are.
To give your agent a server's tools directly instead, add it with -expose mcp.
See and manage them
woodentable mcp list
woodentable mcp tools playwright
woodentable mcp remove playwright
Go deeper with the built-in guides:
woodentable help mcp