Apps (MCP)

Connect external services to your agents using MCP (Model Context Protocol) to extend their capabilities.

Apps (MCP Server) is in BETA.

Apps connect external services to your agents through MCP (Model Context Protocol). Once connected, agents gain access to tools provided by those services and can use them during conversations with your approval.

Recommended Apps

The following apps are pre-configured and ready to connect:

App	Description
Atlassian	Connect to Jira and Confluence for project management and documentation
Linear	Issue tracking and project management
Slack	Connect to your Slack workspace for messaging and notifications
Notion	Access Notion workspaces and pages

Additional apps — including GitHub, GitLab, Google (Gmail, Drive, Calendar), Microsoft (Outlook, OneDrive, Teams), Figma, HubSpot, BigQuery, and more — are being added on an ongoing basis.

Adding a Recommended App

1. Open the agent’s configuration page by clicking the agent name in the sidebar
2. Scroll to the Apps section and click Add app
3. In the modal, select the Recommended tab
4. Click the app you want to connect
5. Complete the OAuth authentication flow when redirected to the service provider

Once connected, the app’s tools are available to the agent in chat.

Access: Private vs. Shared

Every connection has an Access scope that controls who can use it within the project. New connections default to Private — you can change the scope at any time from the App Detail Page.

Access	Who can use it	Whose credentials are used
Private (default)	Only you, in the agent where you connected it	Yours — kept isolated to your user account
Shared	Everyone in the project, including guests	The owner’s — teammates act as the owner in the connected service

Connections are also scoped per agent: connecting Slack in Agent A does not expose that connection to Agent B. Each agent maintains its own credential row, so you can connect the same provider with different accounts in different agents.

Switching a connection to Shared means anyone using the agent will act as you in the connected service. If a teammate had already connected their own account to that provider, their connection is replaced with yours. You must acknowledge this before saving.

Permissions on shared apps

Who can do what depends on the app’s Access scope and the user’s role:

Action	Private app	Shared app
Use the app’s tools	Owner only	Any project member, including guests
Resync tools / edit URL	Owner only	Any non-guest member
Change Access (Private ↔ Shared)	Owner only	Owner (creator) only
Delete	Owner only	Owner (creator) only

Guests can use shared apps in chat but cannot add, edit, resync, or delete them. The dropdown in the agent’s app list hides actions you do not have permission to perform.

Adding a Custom MCP Server

You can connect any MCP-compatible server as a custom app:

1. Open the agent’s configuration page
2. Click Add app in the Apps section
3. Select the Custom tab
4. Fill in:
   • App name (required)
   • MCP Server URL (required)
   • Client ID (optional, for OAuth-based servers)
   • Client Secret (optional, for OAuth-based servers)
5. Click Add to connect

App Detail Page

Click any connected app card in the Apps section to open its detail page.

Connection Details

Next to the app name at the top of the page:

• Connection status — Whether the app is currently connected and accessible
• Last synced — When the tool list was last refreshed from the MCP server

Below that, a card lists:

• MCP server URL — The endpoint this app connects to
• Owner — The team member who connected the app, and when
• Access — Current scope (Private or Shared)

If you are the owner, click Access to switch between Private and Shared at any time. Non-owners see this as read-only.

Tool Permissions

The Tool permissions section lists the tools available to use in the app, organized into two collapsible groups (Read-only and Write/delete) with the tool count shown next to each. Expand a group to see and configure individual tools. Each tool can be set to one of three permission levels:

Permission	Behavior
Always allow	Agent uses the tool automatically without asking
Ask before use	You must approve each use before the agent executes it
Disabled	The agent cannot use the tool

Permission changes are saved automatically.

Tool groups

Tools are automatically grouped by the kind of action they perform:

Group	Meaning	Default permission
Read-only	Does not modify state — typically safe to auto-allow	Always allow
Write/delete	Can modify or delete data — review carefully before allowing	Ask before use

The group is sourced from the MCP server’s annotations. If the server does not report them, Jitera infers the group from the tool name (for example, tools prefixed with get_ or list_ are treated as read-only). You can override the default on any individual tool.

Bulk update

Each group has its own bulk-update control that applies a single permission level to every tool in the group at once. This is the fastest way to onboard a new app — set all read-only tools to Always allow and all write/delete tools to Ask before use in one click, then refine individual tools afterward.

Triggers

If the app provides triggers (events that can start agent actions), they are listed in the Triggers section. Click a trigger to view its details and configuration.

Removing an App

Use the management options on the detail page to remove the app from this agent. The app can be re-added later.

To return to the agent’s configuration page, click the back button showing the agent name at the top of the page.

Related

• Managing Agents — Agent creation and configuration
• Tool Calls / Actions — How agents execute tools in chat
• Automation — Use connected MCP apps in scheduled and webhook-triggered jobs