Jestor MCP Server

Beta: the Jestor MCP server is in beta. Features, limits and behavior may change as we improve it. We'd love your feedback: tell us what works, what doesn't, and what you'd like the assistant to be able to do next. Feature requests are very welcome. Reach out to our support team with your comments.

Connect Jestor to AI assistants such as Claude and Codex through the Model Context Protocol (MCP). Once connected, your assistant can write low-code functions, manage roles, users and tasks, configure no-code (native) automations, build tables and fields, and read, analyze and manage your records, all in plain language.

The assistant always acts as you: it only sees and changes what your Jestor user is allowed to see and change.

Requirements

• A Jestor account on the Pro plan or higher.
• An MCP-compatible AI client (for example Claude or Codex).
• Your regular Jestor login. Authentication uses OAuth, so you never need to copy or paste a token.

Server URL

https://mcp.jestor.com/v1/gateway

Connecting

Claude (web and desktop)

1. Open Settings > Connectors and choose Add custom connector.
2. Enter a name (for example Jestor) and the server URL: https://mcp.jestor.com/v1/gateway.
3. Click Connect and sign in to Jestor in the window that opens.
4. In a chat, enable the Jestor connector from the tools menu.

Codex CLI

Add the server (you can choose any name; we suggest jestor):

codex mcp add jestor --url https://mcp.jestor.com/v1/gateway

A browser window should open so you can sign in. If it doesn't, run:

codex mcp login jestor

(Replace jestor with the name you chose.)

Codex desktop

Open the MCP server settings, add a new server with the URL https://mcp.jestor.com/v1/gateway and complete the sign-in flow.

Other MCP clients

Other clients need to be registered on our side before they can connect. Contact Jestor support with the name of the client you want to use.

What you can do

Low-code functions

Create and maintain Python low-code functions.

• List and search functions, filtering by active status.
• Create a function and set whether it's active and whether it runs asynchronously.
• Write code by creating new versions. Every version is kept with an optional note, so you can review the history.
• Read any version's code.
• Edit a function's name, active status or async setting, or delete it.

Example prompts

• "Write a low-code function that calculates the commission for each closed deal and saves it on the record."
• "Show me the changes between the last two versions of the invoice sync function."

Roles and permissions

Configure permissions and understand who can do what.

• List and inspect roles and their full permission definitions.
• Create roles with their permission settings.
• Edit a role's name, color and permissions.
• Delete a role. Its users are moved to a replacement role you choose.

Each user has one role. To assign or change a user's role, use the Users tools.

Auditing permissions: the assistant can combine the list of users with each role's permissions to build views by app, table, permission or person, and flag users who may have more access than expected.

Example prompts

• "Create a Finance Manager role that can view and edit the Invoices and Payments tables but can't delete records."
• "Create a new role that combines everything Sales and Support can do."
• "Show me everyone who can delete records in the Contracts table."
• "Build a summary of which roles can access each app."

Tip: permission changes take effect immediately for every user in the role. Review the proposed permissions before confirming.

Users

Manage your team in bulk, for example during initial setup.

• List and search users by name, email, status, seat or role.
• Add one user or up to 50 at once, with seat and role.
  • Global users sign in with their email.
  • Local users sign in with a username and password set by you, and don't receive invitations.
• Edit a user's email, seat, role or active status.
• Deactivate users. Data created by them is kept.

Seats: builder, member, request, portal, guest, viewer. Seat limits of your plan apply.

Example prompts

• "Add these 15 people as members with the Sales role: [list of emails]."
• "Move everyone in the Interns role to Viewer."
• "Deactivate [email protected]."

Tasks

Create and manage Jestor tasks for yourself or anyone in your account.

• Create tasks with title, description, priority (not-priorized, low, medium, high, urgent), status (suggestion, open, doing, done, ignored), start and end dates, owners and a checklist.
• Link a task to a specific record in any table.
• Assign to one or more users. If you don't specify an owner, the task is assigned to you.
• Edit any task field, including replacing the checklist.
• List tasks by scope (my tasks, assigned, personal, followed, all), status, priority, owner, related record or creation date. By default only open tasks are listed.
• Delete tasks. Only the person who created a task can delete it.

Example prompts

• "Create a high-priority task for Ana to review contract #312, due Friday."
• "What are my open tasks this week?"
• "Mark all my tasks related to the Acme onboarding as done."

Native automations (no-code)

Use Jestor's library of no-code triggers and actions, also known as native automations, without opening the automation builder.

• Discover which triggers and actions are available for a table.
• Create an automation with one trigger and any number of actions, executed in order. Actions can read from and write to other tables, connected or not.
• Edit an automation's settings and actions. The trigger type can't be changed; create a new automation for a different trigger.
• Enable or disable an automation. This applies to the whole automation (trigger and all its actions).

Common trigger categories include: a record is created, a record is updated, a field changes or matches a condition, and a button is clicked.

Integrations that require a connection: if an action depends on an external provider, the automation is created disabled. Complete the connection in Jestor, then enable it.

Automations only run for events that happen after they are enabled.

Example prompts

• "When a deal in Sales Pipeline changes to Won, create a project in Projects with the same client and notify the account owner."
• "Disable all automations on the Leads table."

Tip: an action that updates records can trigger other automations. Ask the assistant to check for loops before enabling chains of automations.

Tables and fields

Build or extend the structure of your apps.

• Create tables with a name, emoji icon and color.
• Rename tables or change their icon.
• Create fields in batches, including relationships to other tables, so a full table can be set up in one step.
• Edit fields: rename them and change their options. A field's type can't be changed after it's created.

Supported field types

Some advanced settings (for example relationship filters, date display format or attachment limits) are not yet available through MCP and use Jestor's defaults. You can adjust them in the Jestor interface.

Example prompts

• "Create a Projects table with name, client (connected to Clients), start date, budget in USD and a status field with Planning, In progress and Done."
• "Add a priority field with Low, Medium and High to the Tickets table."

Analytics and SLA metrics

Ask questions about your data and get aggregated answers without building a report.

Aggregates

• Operations: count, sum, avg, min, max.
• Group results by any field (status, owner, category, etc.).
• Supports the same filters as record search.
• Based on record creation date. The window can be up to 3 months; if you don't give dates, the last three calendar months are used.

Example prompts

• "How many support tickets were opened per category last month?"
• "What's the average deal value by salesperson this quarter?"

SLA metrics

Available on Scale and Expert plans.

Get the same SLA metrics you see in Kanban views, aggregated over a period and combined with any filter.

• Stage mode: how long records spend in each stage (records count, transitions count, total, average, minimum and maximum duration), optionally split by stage.
• Terminal mode: how long records take to reach a final state (records count, completed count, completion rate, and total, average, minimum and maximum time to completion). You tell the assistant which values count as "completed".

Only fields with SLA enabled can be analyzed. If a table has more than one, the assistant will ask which one you mean.

Example prompts

• "In the Tickets table, what's the average time each ticket stays in 'Waiting for customer'?"
• "What percentage of onboarding projects created in August reached 'Live', and how long did it take on average?"

Records

Work with the data inside any table you have access to.

• Read: search records with filters, sorting and pagination. The assistant can page through an entire table, so analyses are not limited to a small sample.
• Create: add one record or up to 50 at a time. Useful for importing lists or generating realistic test data for a new app.
• Update: change any fields of a record.
• Delete: archive up to 100 records at a time. Archived records go to Jestor's trash and can be restored from the Jestor interface.

Filter operators: ==, !=, >, <, >=, <=, like, not like, starts, in, between, is_null, is_not_null, null_or_empty. Filters are combined with AND, with OR groups for alternatives.

Example prompts

• "List all deals in the Sales Pipeline table with value above 50,000 that are still open."
• "Create 20 sample customers in the Clients table so I can test my new app."
• "Change the status of order #1842 to Shipped."
• "Archive every lead created before January that has no email."

Tip: before bulk updates or deletions, ask the assistant to list the affected records first and confirm them.

Limits

Security

• OAuth sign-in: the assistant uses your own Jestor session. No API tokens to manage.
• Your permissions apply: the assistant can't see or change anything your user can't.
• Recoverable deletes: records are archived, not permanently erased, and users are deactivated rather than deleted.
• Plan rules apply: seat limits and plan features are enforced the same way as in the Jestor interface.

Most AI clients ask for your confirmation before running actions that change data. We recommend keeping these confirmations on, especially for bulk operations.

FAQ

Which plan do I need?
The MCP server is available on Pro and higher. SLA metrics require Scale or Expert.

Can I restore archived records through the assistant?
Not yet. Restore them from the trash in the Jestor interface.

Can the assistant delete automations?
Not currently. It can disable them, which stops them from running.

Does the assistant see data from other accounts?
No. It only accesses the Jestor account you signed in with, within your permissions.

My client isn't listed. Can I still connect?
Contact Jestor support. We need to register the client before it can connect.

How do I send feedback or request a feature?
The MCP server is in beta and your input shapes what we build next. Contact our support team with feedback, bugs or requests for new capabilities.