Skip to content
GlxymeshDocs
Get started: set up a projectInstall the gxmesh CLI, create a Glxymesh project in Go, TypeScript or Python, add a tool, run it locally, deploy it, and connect Claude Code.Learn the CLI step by stepUnderstand the gxmesh workflow from sign-in and project selection to scaffolding, local calls, tests, deployment and client connection.Understand gx.yml and templatesLearn YAML syntax, every project setting, tool definitions, input placeholders, secrets, network rules and tests through a complete HTTP tool.How Glxymesh runs your toolsOrganizations, projects and tools; the tool kinds; what happens on a tool call; OAuth 2.1 sign-in with no API keys; and the network rules every tool runs under.
Connect an MCP clientConnect Codex, Claude, Claude Code, VS Code, Cursor, Windsurf and other MCP clients to a Glxymesh project over Streamable HTTP with OAuth, step by step, and fix 401/404/405.WhatsApp accessLink your WhatsApp number to use Ada with the projects you allow.
Build tools with AIDescribe a tool in plain language and let Ada write and check it in Mesh Builder, or have your own agent propose one, then review, test and publish it from the console.Build from GitHubTurn your own API's routes into MCP tools straight from its GitHub repository, and on Pro, keep them in step with every push.ChatboxPut Ada on your own website. The same assistant, tools and team Inbox as your WhatsApp support desk, in a chat widget you add with one script tag.Tool kindsThe two kinds of Glxymesh tool, http and function, with a complete tool.yml for each and when to use which.Develop locallyRun every tool in a Glxymesh project on your machine with gxmesh dev, call tools from the terminal, run their tests, and connect a local MCP client.Deploy and roll backWhat gxmesh push does, approving new hosts and keys, the tests that run before a revision goes live, revisions, rollbacks, and watching calls.Keys and network accessHow Glxymesh tools reach external APIs, how new hosts are approved, and how API keys are added on the way out so tool code never holds them.Connect to a databaseReach Postgres, MySQL, Redis, MongoDB and other TCP services from a Glxymesh function tool, with the address approved in tool.yml and the password passed in from the vault.Project layoutEvery file in a Glxymesh project for Go, TypeScript and Python, who writes it, whether to commit it, and the naming rules the CLI enforces.
gxmesh CLI referenceEvery gxmesh CLI command for Glxymesh projects: login, org and project scope, init, pull, new, gen, dev, call, test, push, revisions, rollback, connect, update, uninstall and env vars.gx.yml referenceEvery field in gx.yml, the Glxymesh project file that sets the organization, project, language, server identity and defaults for every tool.tool.yml referenceEvery field in tool.yml, the Glxymesh tool file, for http and function tools, with input types, output formats, network, keys, limits and tests.SDK referenceThe ctx object every Glxymesh function tool receives, in Go, TypeScript and Python, for outbound HTTP, key placeholders, logs, the caller, the deadline and errors.LimitsLimits for Glxymesh projects and tools: tool.yml sizes, time and memory per call, outbound requests, push size, sleep and keeping tools awake.PricingFree, Pay as you go, Pro and Business plans, usage balances and AI credits.
Open the consoleplatform.glxymesh.comGo to glxymesh.comwww.glxymesh.com
↑↓ navigate↵ openCtrl↵ new tabesc close
glxymesh.com
Select theme
Open console
Reading time 2 min

Limits

Limits for Glxymesh projects and tools: tool.yml sizes, time and memory per call, outbound requests, push size, sleep and keeping tools awake.

Tools

Section titled “Tools”
Limit Value
Tool name 1–64 characters of a-z, 0-9, -
Description 10–2,000 characters
Inputs per tool 50
Input description 500 characters
Allowed hosts per tool 20
Keys per tool 20
Tests per tool 50
Title 80 characters

Calls

Section titled “Calls”
Limit Value
Time per call 10s unless gx.yml or tool.yml sets it; 1 second to 15 minutes
Memory 128 MB to 10 GB, set by limits.memory. A project’s function tools share the largest any of them asks for.
Log lines kept per call 64 KB
Calls a second, per organization Free 5 · Pay as you go 20 · Pro 50 · Business 200
Calls running at once, per organization 100 on every plan

A call refused for either of the last two answers with JSON-RPC error -32005, is not billed, and can be tried again a moment later. A project admin can also set how many times a day one person may call a tool; that refusal says when the count resets (00:00 UTC).

Outbound requests

Section titled “Outbound requests”
Limit Value
Schemes https, and TCP to the host:port pairs in network.connect (function tools); no UDP
Destinations Hosts in the tool’s network.allow and their subdomains; never private or internal addresses
Response per request 4 MB
Connecting 5 seconds, then the request fails

Projects

Section titled “Projects”
Limit Value
Languages Go, TypeScript (Node.js) and Python 3.14
Push size 6 MB of source, before packages are installed
Project and organization slugs 1–40 characters of a-z, 0-9 and single hyphens

Sleep

Section titled “Sleep”

A project’s function tools sleep after 7 days without a call, and wake on the next one. http tools never sleep. Tools you keep awake from the console’s Tools page never sleep:

Free Pay as you go Pro Business
Tools kept awake — — 5 50

For what each plan includes in calls, compute, members and AI credits, see pricing.

© 2026 Glxymesh