Turn your API into MCP tools from its GitHub repository
Point Mesh Builder at your API's GitHub repo and Ada writes one MCP tool per route. On Pro, every push updates only the tools it affects, as a draft you review.
In this post
- Connect GitHub (read-only)
- Build tools from one folder
- What Ada reads, and what she never reads
- Keep tools in step with every push
Your API already exists. Writing an MCP tool for every route by hand is slow, and the tools drift as the API changes. Instead, point Mesh Builder at the repository. Ada reads the routes and writes a tool for each one. On Pro and Business, she keeps them up to date with every push.
Nothing goes live on its own. You review every draft and publish it.
Connect GitHub#
Glxymesh reads repositories through its own GitHub App. You choose which repositories it may see.
- In the console, open Mesh Builder, choose New build, then GitHub repository.
- Choose Install on GitHub, pick the account and repositories, and install.
- GitHub sends you back and the account appears. Use Add account for another person or organization.
If a colleague already installed the app, choose Link it and sign in with GitHub instead.
| The app can | Why |
|---|---|
| Read repository contents | To read the folder you pick, and what a push changed |
| Read metadata | To list your repositories and branches |
| Receive push events | To hear about pushes, for automatic updates |
Build tools from a folder#
Pick the account, the repository, the branch and the folder your API lives in, such as /services/api. Use / for the whole repository. Then choose Use this repository and start the build.
Ada uses an OpenAPI or Swagger file if the folder has one. Otherwise she reads the routes in the code and how requests are authenticated. She writes one tool per route, and leaves out admin and internal routes unless you ask for them.
Your API's address and key are stored in the project's vault as you review the draft, under names like BILLING_API_HOST and BILLING_API_KEY. Ada never sees either.
What Ada reads, and what she doesn't#
| Read | Never read |
|---|---|
| One folder of one branch, at the latest commit | Key and env files: .env, *.pem, *.key, credentials.json |
| Up to 5,000 files and 16 MB | Dependency and build folders: node_modules, vendor, dist |
| Text files up to 256 KB | Binary files |
Anything in the code that looks like a live credential, such as an sk_live_ key, is removed before Ada reads it. The folder is deleted after the build.
Keep tools in step with every push#
On Pro and Business, switch on Update the tools when this branch changes. From then on, each push to that branch is checked:
- Docs, tests or CI only? The push is skipped at once, with no AI credits spent.
- No route changed? Most pushes, like a refactor or a bug fix inside a handler, stop here. No draft, no email.
- A route changed? Ada updates only the tools that call it, adds tools for new routes and removes tools whose route is gone.
- Tested, then emailed. You get an email with what changed and a Review the draft link.
Publish the draft and the tools keep the same address and sign-in, so Claude Code, Cursor and your other clients stay connected.
To stop updates, open a build in that project and choose Turn off updates from GitHub. The full guide is Build from GitHub.
Explore MCP guides by task: creation, hosting, connections and security.
