DocsHow to set up MCP integrations without using terminal

How to set up MCP integrations without using terminal

Use Case: When you want to connect tools like Jira, Slack, or Linear without touching config files or terminal Time to Complete: 5 minutes per integration Prerequisites: Worklayer installed, Claude account, tool accounts (Jira, Slack, etc.)

Quick Answer

In Worklayer, set up MCP integrations using the MCP Manager UI—no terminal required. Click "Add MCP," select your tool (Jira, Slack, Linear), enter credentials via form fields, and test the connection. All setup happens through the app interface.

Step-by-Step Instructions

Step 1: Open MCP Manager

Access the MCP Manager through the Home view or Settings.

How to open:

  • Click Home → Add MCP
  • Or Settings → MCP Manager

Step 2: Browse Available Integrations

View the list of available MCP connectors.

Common integrations:

  • Jira (issue tracking, sprint data)
  • Slack (channel messages, posting updates)
  • Linear (issue tracking, project data)
  • GitHub (repository data, pull requests)

Step 3: Select Integration

Click on the integration you want to connect.

Example: Connecting Jira

  1. Click "Jira" in the integrations list
  2. MCP Manager shows a form with required fields

Step 4: Enter Credentials

Fill in the form fields (varies by integration).

Example: Jira requires:

  • Jira instance URL (e.g., yourcompany.atlassian.net)
  • Email (your Jira account email)
  • API token (from Jira settings)

Example: Slack requires:

  • Workspace URL
  • OAuth token or bot token

Step 5: Test Connection

Click Test Connection to verify Worklayer can access the tool.

Expected results:

  • ✓ Connection successful: "Connected to [Tool Name]"
  • ✗ Connection failed: Error message with troubleshooting steps

Step 6: Use Integration

Once connected, AI can access the tool in chat.

Example:

Pull open bugs from Jira and show priority distribution.

Example: End-to-End Workflow

Let's connect Jira without using terminal.

Step 1: Open MCP Manager:

  • Click Home → Add MCP

Step 2: Browse integrations:

  • See list: Jira, Slack, Linear, GitHub, Google Drive
  • Select "Jira"

Step 3: MCP Manager shows Jira form:

Jira Integration Setup Jira Instance URL: [text field] Email: [text field] API Token: [password field] [Test Connection] [Cancel]

Step 4: Enter credentials:

  • Jira Instance URL: worklayer.atlassian.net
  • Email: founder@worklayer.pro
  • API Token: ATATT3xFfGF0... (paste from Jira settings)

Step 5: Click Test Connection:

✓ Connected to worklayer.atlassian.net Projects accessible: 3 (WORK, BUG, ALPHA)

Step 6: Use integration in chat:

Pull all open P1 bugs from Jira project WORK.

AI returns:

Found 3 P1 bugs in WORK project: | Key | Summary | Status | Assignee | |---|---|---|---| | WORK-101 | Visual mode crashes | In Progress | You | | WORK-103 | MCP fails silently | To Do | Unassigned | | WORK-105 | Skill builder validation | To Do | You |

Integration works.

Time: 5 minutes, no terminal used

Tips & Best Practices

  • Start with one tool: Connect your most-used tool first (usually Jira or Linear) before adding others.
  • Use dedicated API tokens: Create tool-specific API tokens (not personal access tokens) so you can revoke them independently.
  • Test after setup: Always click "Test Connection" after entering credentials to verify the integration works.
  • Check permissions: Some integrations require specific permissions (e.g., Jira needs "read issues" permission). Check tool documentation if connection fails.
  • Reconnect if needed: MCP Manager lets you disconnect and reconnect anytime. If an integration stops working, try reconnecting.

Common Mistakes to Avoid

  • Using incorrect URL format: Most tools expect instance name only (worklayer.atlassian.net), not full URL (https://worklayer.atlassian.net). Remove https:// prefix.
  • Using password instead of API token: Tools like Jira require API tokens, not account passwords. Check tool documentation for how to generate tokens.
  • Not granting required permissions: If integration fails with "403 Forbidden" error, check that your API token has sufficient permissions (read issues, read projects, etc.).
  • Skipping the test: Don't assume the integration works. Always click "Test Connection" to verify before using the integration.

Related Articles