Skip to main content
Glama
Sign In

Xyvenra

by io.github.LAHutchins91
OverviewDiscussionsAdmin

Server Details

Create Xyvenra Cloud sites and Data projects, deploy static HTML, and query Data.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
47.4% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
ChatGPT
–
Claude
–

TDQS

B3.3/5.0

Scored across 11 tools

Disambiguation3/5

The descriptions work hard to draw boundaries ("this is not a websocket", "Data tables and records use the database tool"), which helps, but several tools are broad multi-resource catch-alls whose single-word names give no hint of scope: `project` reads/saves Cloud, Studio, and Mobile objects while `database`, `files`, and `env_vars` each hide full CRUD surfaces. The `create_project` / `list_projects` / `project` trio sits close together and relies entirely on prose to separate them.

Naming Consistency2/5

Only `create_project` and `list_projects` follow a verb_noun pattern; the rest are bare nouns (`database`, `files`, `project`, `status`, `export`, `guidance`) or an underscored namespace prefix (`eas_dispatch`). No predictable verb convention is established, so an agent cannot infer whether a tool creates, reads, or mutates from its name alone.

Tool Count4/5

Eleven tools is a reasonable count for a multi-product platform surface, and each entry maps to a recognizable product area. However, several tools bundle many operations (table CRUD plus record CRUD plus polling in `database`), so the effective capability surface is much larger than 11 suggests and arguably deserves finer-grained splitting.

Completeness4/5

Coverage across Cloud, Data, Studio, Mobile, and Code is broad: project lifecycles, deploys, exports, record/table management, private files, env vars, plus status and guidance flows. Gaps exist — there is no delete/archive for projects or sites, no deploy history or rollback, and no domain management — but the stated scope explicitly excludes auth, edge functions, and Node runtimes, so these are mostly recoverable omissions.

Available Tools

11 tools
create_projectCreate projectAInspect

Create a Cloud site, Data project, Studio browser app, or Mobile Expo starter for this account. Code stays in the browser and has no server-side project. Nothing is deployed or charged.

Inputs: name (required), product (required), slug.

databaseDatabaseA
Destructive
Inspect

List or create Data tables, delete a table, and list, query, get, create, batch-create, update, or delete records on a Data project this account owns. list_records accepts the same filter, search, order, and cursor as the project Data API and applies them to the latest 250 rows. list_changes polls records updated after since. Field changes stay in the Data app. This is not a websocket, Supabase Realtime, Auth, or Edge Functions. Private files are the files tool.

Inputs: action (required), projectId (required), q, op, +15 more.

deployDeploy siteAInspect

Publish self-contained HTML to a Cloud site this account owns. Pass projectId instead of html to send a saved Studio page. Public env vars for that site are written into the static page. Private values are not. Cloud is not a Node host. ZIP uploads stay on POST /api/cloud/v1/{siteId} with a Cloud deploy key.

Inputs: siteId (required), html, projectId.

eas_dispatchCustomer Expo workflowB
Destructive
Inspect

Dispatch an existing workflow on the customer’s Expo project with the Expo token they supply for this call. The token is not stored. The in-app starter is not uploaded. Xyvenra does not pay Expo. Do not call this from guidance.

Inputs: appId (required), token (required), gitRef (required), workflowFile (required).

env_varsEnvironment variablesA
Destructive
Inspect

List, set, update, or delete owner-scoped env vars for Cloud, Data, Mobile, Studio, or the Code workspace. exposure is secret by default. Cloud publish writes public values into the static page and leaves private values out. There is no server runtime.

Inputs: product (required), name, value, action, +2 more.

exportExport projectA
Read-only
Inspect

Export an owned Studio source ZIP, Mobile Expo project ZIP, or Data project JSON. Does not start an EAS build, publish a site, or run a server. Code has no server-side export.

Inputs: product (required), projectId (required).

filesData filesA
Destructive
Inspect

List, upload, download, or delete private files on a Data project this account owns. Uploads are base64, at most 1 MB, within 100 files and 50 MB per account. This is the existing private bucket, not a public Supabase Storage bucket.

Inputs: projectId (required), name, action, fileId, +2 more.

guidanceNext stepCInspect

Ask once, calmly, about real next steps across Cloud, Data, Mobile, Studio, Code, and the MCP plugin. Default is to offer the next step. Decline turns a path off. continue creates only the step you name. It does not deploy or charge. If guidancePending is true on status, call this once with action ask.

Inputs: product (required), name, path, slug, +2 more.

list_projectsList projectsA
Read-only
Inspect

List Cloud sites, Data projects, Studio apps, or Mobile starters owned by this account. Code returns the browser-workspace note.

Inputs: product (required).

projectRead or save a projectA
Destructive
Inspect

Read a Cloud page, Studio source, or Mobile Expo draft this account owns. Save replaces Studio source or a Mobile draft and does not publish, start an EAS build, or charge. A Mobile save requires expectedUpdatedAt from the last get or save. Publish Cloud HTML with deploy. Code has no server-side project. Data tables and records use the database tool.

Inputs: action (required), product (required), projectId (required), html, +5 more.

statusStatusB
Read-only
Inspect

Show Code, Cloud, Data, Mobile, and Studio for this account. guidancePending means the one-time next-step ask has not been recorded. Do not repeat that ask after guidance says it was already asked.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources