Skip to main content
Glama

Prepare a form starting point for review

Typeform + your AI assistant · powered by PipMCP

You want to prepare a form starting point for review, using the account your team has actually connected.

Made for: Teams collecting customer feedback

For real use, you will need PipMCP and access to Typeform.

Ask your AI to set this up

Paste this into a coding assistant that can open project files and run commands, such as Codex, Claude Code or Grok Build. You do not need to understand the code first.

Help me use this project: https://github.com/jannikco/typeform-mcp

I'm not a programmer. My goal is: Prepare a form starting point for review.

Read the project instructions and set it up in a new folder without overwriting my work.
Guide me through PipMCP and its private key setup; never ask me to paste secrets into this
chat. Run a documented sample-data demo if available, then help me get a first small
result from my connected app. Explain the result in plain English. Ask before changing
records, sending messages or publishing anything.

Related MCP server: FormVault MCP Server

Three useful things to ask for

Show the available forms.
Prepare a new empty form from my brief and ask before creating it. Make clear which
questions still need to be configured.
Turn the form list into a simple survey inventory for our customer-feedback planning
session.

Your path to a real result

flowchart LR
  A["Ask your AI"] --> B["Connect PipMCP"] --> C["Prepare a form<br/>starting point for<br/>review"] --> D["Review together"]
  1. Open PipMCP setup and sign in or create your account.

  2. Connect the app in PipMCP with the permissions you want to grant.

  3. Create the product API key through the official setup, add it privately to your AI project's environment, and ask your AI to try a small read.

What to expect: Connect Typeform in your PipMCP account, then use your PipMCP key for the supported actions. Review proposed changes before they are sent. This client can create an empty form. Its questions and final publication still need review.

Add your PipMCP key privately in your project settings. Keep keys out of chat and public repositories.

Keep going

Typeform MCP server

Use Typeform from Claude Code, Codex, Grok Build and MCP clients through PipMCP. One PipMCP API key connects this package to private execution.

Activate with PipMCP · Integration directory

Build something useful

List forms and explicitly create a new empty form for later review.

The package is an authenticated client: discovery, schemas, policy decisions and execution come from PipMCP. Provider implementation remains on the server.

Quick start

Requires Node.js 22+. Clone this repository, then:

npm ci --ignore-scripts
npm test
npm start
# After configuring your provider in PipMCP and setting PIPMCP_API_KEY:
npm start -- --live
# Launch the stdio MCP bridge:
npm run server

Create a PipMCP API key with explicit connectors:read and connectors:call scopes. Set PIPMCP_API_KEY in the calling process environment. Provider credentials are configured in PipMCP. Multiple accounts require explicit PIPMCP_INTEGRATION_ID and PIPMCP_CONNECTION_ID from discovery. Existing keys do not gain scopes automatically.

Built for coding agents

Install this repository's skill into your project:

node lib/cli.mjs agents install --client codex --scope project --project /path/to/project
# Use claude or grok for those clients.

Connect AI agents to Typeform using one PipMCP API key and actual hosted tool discovery. Native AGENTS.md, CLAUDE.md and project skills support the current coding session. No additional AI model key is required. capabilities.json describes the package; llms.txt indexes its instructions.

Inspect actual tools before calling

import {PipMCPGatewayClient} from './lib/index.mjs';
const client = new PipMCPGatewayClient(); // PIPMCP_API_KEY
const inventory = await client.getTools("typeform");
console.log(inventory.data.tools);
// Select a real tool and validate your arguments against its returned schema.
// client.callTool(provider, actualToolName, reviewedArguments, {idempotencyKey});

PipMCP enforces workspace, role, connection, policy/approval and usage controls. Preserve the original idempotency key when retrieving/resuming a receipt. Pending and confirmation_required are not completed provider results; uncertain writes are held for reconciliation. The bridge never auto-approves a hosted action.

Version 1 migration

This release uses the authenticated PipMCP gateway for real discovery/execution. Upgrade your MCP launch command and configure PIPMCP_API_KEY before reconnecting. Historical local runtimes remain available under their original MIT license in Git history.

Evidence and support

Transport, package and agent fixtures are tested. Authentication/provider access must be checked in your own configured workspace; synthetic fixtures do not establish live provider execution. Do not include credentials or customer records in public issues. MIT covers this public client.

Provider setup reference

Official provider documentation. Credentials are entered in PipMCP; this package does not accept or store provider secrets.

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

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes the Filly Forms REST API as MCP tools for AI agents, enabling form type listing, record CRUD, data preview, and document upload with AI extraction.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and MCP clients to discover and call hosted CRM tools through a single PipMCP API key, with governed execution, schema validation, policy controls, and idempotency keys.
      21 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI agents and MCP clients to Jotform through a single PipMCP API key, exposing hosted tool discovery and governed execution so agents can find authorized forms and read bounded pages of their submitted responses. Policy, approval, and usage controls are enforced server-side, with no provider credentials stored in the package.
      MIT