Can I use Gravity Forms as a CLI?

Yes. KosmoKrator exposes a Gravity Forms CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Gravity Forms through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Gravity Forms tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Gravity Forms credentials stored?

Gravity Forms credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Gravity Forms MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Gravity Forms MCP Integration for LangChain

Connect Gravity Forms to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write API key auth

Submit Gravity Forms feedback View package source

Connect Gravity Forms to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Gravity Forms MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-gravity": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=gravity",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=gravity --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Gravity Forms instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Gravity Forms Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Gravity Forms integration catalog.

MCP tool	Source function	Type	Description
`integration__gravity__gravity_list_forms`	`gravity.gravity_list_forms`	Read	List forms available in Gravity with optional pagination.
`integration__gravity__gravity_get_form`	`gravity.gravity_get_form`	Read	Get details for a specific Gravity form.
`integration__gravity__gravity_submit_form`	`gravity.gravity_submit_form`	Write	Submit a Gravity form with field values.
`integration__gravity__gravity_list_submissions`	`gravity.gravity_list_submissions`	Read	List submissions for a specific Gravity form.
`integration__gravity__gravity_list_entries`	`gravity.gravity_list_entries`	Read	List entries for a specific Gravity form.
`integration__gravity__gravity_get_entry`	`gravity.gravity_get_entry`	Read	Get details for a specific Gravity entry.
`integration__gravity__gravity_get_current_user`	`gravity.gravity_get_current_user`	Read	Get profile information for the authenticated Gravity user.

Related Gravity Forms Pages

Gravity Forms CLIUse direct JSON commands instead of MCP discovery. Gravity Forms MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.