ObjectStack

Connect Gemini CLI to any ObjectStack deployment — cloud or self-hosted — over the Model Context Protocol. Discover objects, query and change records, and run business actions, all under your own permissions and row-level security.

One extension serves every deployment: the deployment URL is the only per-environment input (OBJECTSTACK_MCP_URL). Identity is self-serve — every ObjectStack deployment is its own OAuth 2.1 authorization server with Dynamic Client Registration.

Install

gemini extensions install https://github.com/objectstack-ai/gemini-extension

Connect

Set the deployment URL (find it on your deployment's Setup → Connect an agent page, or append /api/v1/mcp to the address you open in the browser):

export OBJECTSTACK_MCP_URL="https://acme.objectos.app/api/v1/mcp"

Headless (CI, machine accounts): configure an ObjectStack API key as an x-api-key header on the MCP server entry in your Gemini settings instead of OAuth.

What's inside

• GEMINI.md — the portable ObjectStack agent context: discover-first workflow (list_objects → describe_object → act), the full tool surface incl. business actions (list_actions/run_action), and governance conventions. It enumerates no schema — objects and actions are discovered live, so one install keeps working as your apps evolve.
• gemini-extension.json — MCP server bound to $OBJECTSTACK_MCP_URL.

GEMINI.md is a copy of the single source in @objectstack/mcp (renderSkillMarkdown(), frontmatter stripped); CI fails on drift. Re-render with npm run sync:skill — never hand-edit.

License

Apache-2.0 — see LICENSE.