Connect your AI to Tessryx over MCP
Tessryx runs an MCP server, the standard way AI assistants connect to outside tools. Add it to the assistant you use and it can build in your workspace while you talk to it, from the data model through to the pages.
The dashboard has quick setups for Claude, ChatGPT, Cursor, VS Code, Goose, Claude Code and Grok. Anything else that speaks MCP over HTTP with OAuth can connect with the server address.
Try it
The tools your AI gets
Connect from
Open Claude's connector dialog. Tessryx is already filled in.
Approve it on the Tessryx consent screen and pick the workspace it builds in.
Then it can call
90of 93 tools
Maintainer. Builds: schemas, workflows, pages, integrations, schedules and apps, and sees secret names.
Getting its bearings3/3
Apps13/13
Schemas7/7
Content records8/8
Workflows and runs15/15
Pages and routes12/12
Integrations10/10
Schedules14/14
Custom domains2/5
Media2/2
Secrets, by name only2/2
Dependency graph2/2
Point at a tool to see what it does. A dimmed one shows the message your AI gets.
- Reads
- Changes
- Can publish
- Deletes or overwrites
- Runs or reaches out
No tool can read a secret's value or change members and billing. A connection stays in the workspace you approved.
How it works
- 01
Pick a workspace when you connect
The consent screen asks which workspace the assistant may use, and the connection stays pinned to it. To build somewhere else, connect again and pick that one.
- 02
It works with your role
Each tool call is checked against your role in that workspace. It can't read secret values or your password.
Questions
Is there a charge for the AI itself?
Tessryx doesn't bill for model usage. You bring the assistant and its subscription, and runs of what gets built use credits.
How do I disconnect it?
Open Account security and disconnect it under connected apps. Access ends straight away, and what it built stays.
Under the hood
The technical details
- protocol
- MCP over Streamable HTTP at https://mcp.tessryx.io, with OAuth 2.1: authorization code with PKCE, dynamic client registration (RFC 7591) and protected-resource metadata (RFC 9728).
- clients
- One-click for Claude and ChatGPT; install links for Cursor, VS Code and Goose; a command for Claude Code; a config block for Windsurf, Cline and the rest; a walkthrough for Grok.
- tools
- 93 tools, each with a title and read-only or destructive hints.
Related features
Your AI runs and checks what it builds
Your AI can make and change anything in your workspace and publish it. When something it built fails, it can run it again and read the error itself.
You approve which workspace it uses
When you connect, a Tessryx consent screen asks which workspace the assistant may build in, and a code sent to your email confirms it.
Bring your own AI, with no markup
You build with the assistant and subscription you already have, and AI steps in your workflows run on your own model key. Tessryx doesn't bill for model usage at all.
Guides written for your AI
Tessryx gives your AI short guides on how the pieces fit together, plus recipes for common builds like a blog, and it reads them before it starts building.