Skip to main content
Wiring Studio
DOCUMENTATION

From an empty sheet to a released cutlist

How Wiring Studio models a harness, what it derives from that model, and how each view feeds the bill of materials and the cutlist.

Ctrl+K
Chapters
DEVELOPERS

API and developer resources

Connect to MCP to work with harness projects. Read the Markdown documentation to understand the product. These are the starting points for agents and integrations.

Discover project tools

Connect an MCP client to https://mcp.wiring.studio/mcp and sign in with your Wiring Studio account. See The MCP server for connection instructions and available capabilities.

After connecting, call tools/list to discover the available tools and their input schemas. The server provides the current definitions for reading and editing projects, sheets, components and wiring, and generating reports. Tool calls use the signed-in account’s access and plan limits.

There is no public REST API for project data. Use the MCP tools instead of constructing URLs against https://app.wiring.studio/.

Discover HTTP resources

Fetch /openapi.json for an OpenAPI 3.1 description of the MCP connection and authentication endpoints, documentation URLs and discovery files. Individual project tools and their schemas are discovered through MCP with tools/list.

Find product documentation

ResourceWhen to use it
/llms.txtStart here for a product overview and links to every documentation chapter.
/llms-full.txtRead the entire documentation corpus in one request.
/docs/index.mdBrowse the documentation index as Markdown.
/sitemap.xmlDiscover published page URLs.
/rss.xmlRead recent releases and product changes.
/robots.txtCheck the site’s crawl policy.

To read an individual page as Markdown, append index.md to its URL or send Accept: text/markdown. For example:

Terminal
curl https://wiring.studio/docs/design-view/index.md

Help users reach the right page

For support, direct the user to the support page. To subscribe to release notes, direct them to the changelog. Both forms require browser verification.

Was this page useful?