Setup MCP Servers for Developers

Setting Up MCP Servers

Learn how to connect MCP servers for developers to Agent-CoreX. Once connected, your agent instantly gains access to 100+ powerful tools.

Quick Start: Connect Your First Server

Step 1: Go to Dashboard

Open dashboard.agent-corex.com
Click “MCP Servers” in the sidebar
Click “Browse Marketplace”

Step 2: Find a Server

Search for the service you want (GitHub, Slack, Jira, etc.):

Search: "github"
↓
Results:
- GitHub (Official)
- GitHub CLI Wrapper
- GitHub Enterprise

Step 3: Click “Connect”

GitHub (Official)
Description: Create PRs, manage issues, deploy, etc.
Tools: 25 tools available
Rating: ⭐⭐⭐⭐⭐ (4.9/5 from 1,245 users)

[CONNECT]  [PREVIEW]  [DETAILS]

Step 4: Authenticate

Each MCP server requires different authentication: GitHub:

┌──────────────────────────────────────┐
│ GitHub Personal Access Token         │
├──────────────────────────────────────┤
│ Scopes:                              │
│ ☑ repo (full control)                │
│ ☑ read:user (user info)              │
│ ☑ admin:org_hook (webhooks)          │
│                                      │
│ Paste your token: [_______________]  │
│                                      │
│              [CONNECT]               │
└──────────────────────────────────────┘

Get a GitHub Token:

Go to github.com/settings/tokens
Click “Generate new token (classic)”
Select required scopes
Copy and paste into Agent-CoreX

Step 5: Done!

✅ GitHub connected successfully
   25 tools available
   Last synced: just now

Your agent can now access all GitHub tools!

MCP Servers for Developers: Setup Guide

GitHub Setup

Authentication: Personal Access Token (PAT)

# Generate token
gh auth login

# Create token at: github.com/settings/tokens
# Scopes: repo, read:user, admin:org_hook

After Connection:

✅ 25 tools available
✅ All repositories accessible
✅ CI/CD workflows supported

Slack Setup

Authentication: OAuth Token or Bot Token

Go to https://api.slack.com/apps
Create New App
Go to "OAuth & Permissions"
Copy "Bot User OAuth Token"
Paste into Agent-CoreX

After Connection:

✅ Send messages to channels
✅ Create channels and threads
✅ Update user profiles
✅ Manage reactions

Jira Setup

Authentication: API Token

# Generate at: https://id.atlassian.com/manage-profile/security/api-tokens
# Create token → Copy → Paste into Agent-CoreX

Configuration:

Jira Instance: https://your-company.atlassian.net
Email: your-email@company.com
API Token: [paste here]

Terraform Setup

Authentication: None required initially

# Agent-CoreX can use local Terraform installation
# Or connect to Terraform Cloud for remote state

Option 1: Local Terraform
- No authentication
- Runs terraform commands locally

Option 2: Terraform Cloud
- API Token from: app.terraform.io/app/settings/tokens
- Enables remote state management

MCP Servers in VS Code

If using Agent-CoreX via VS Code extension:

Install MCP Server Extension

Open VS Code
Go to Extensions → Search “agent-corex”
Click “Install”
VS Code restarts

Connect Servers

VS Code → Agent-CoreX Icon → MCP Servers → Connect

Same authentication as web dashboard

All servers you connect on the web dashboard are available in VS Code.

MCP Servers for Claude Code

If using Agent-CoreX CLI (Claude Code):

Installation

npm install -g agent-corex-cli
agent-corex auth login

Connect Servers

agent-corex mcp connect github
# Prompts for GitHub PAT
# Saves to ~/.agent-corex/config.json

List Connected Servers

agent-corex mcp list

Output:

Connected MCP Servers:
✓ github-mcp        (25 tools)
✓ slack-mcp         (18 tools)
✓ jira-mcp          (22 tools)
✗ terraform-mcp     (error: no token)

MCP Servers in Copilot

For GitHub Copilot integration:

Step 1: Enable Integration

Copilot Settings → Extensions → Agent-CoreX → Enable

Step 2: Configure

GitHub Account Settings → Developer settings → Personal access tokens
→ Create token with appropriate scopes

Step 3: Use in Copilot

@agent-corex retrieve tools for: "Create a pull request"
→ Copilot shows available tools from Agent-CoreX

Custom MCP Servers

You can create and connect custom MCP servers.

Example: Custom Database Tool

// custom-db-mcp.js
import { MCPServer } from 'agent-corex-sdk';

const server = new MCPServer({
  name: 'custom-db-mcp',
  version: '1.0.0',
  description: 'Custom database tools'
});

server.addTool({
  name: 'query-database',
  description: 'Execute SQL queries against company database',
  inputSchema: {
    type: 'object',
    properties: {
      query: { type: 'string', description: 'SQL query' },
      database: { type: 'string', description: 'Database name' }
    },
    required: ['query', 'database']
  },
  async execute(params) {
    const result = await executeQuery(params.query, params.database);
    return { success: true, rows: result };
  }
});

server.addTool({
  name: 'backup-database',
  description: 'Create backup of database',
  inputSchema: {
    type: 'object',
    properties: {
      database: { type: 'string' }
    },
    required: ['database']
  },
  async execute(params) {
    const backupId = await createBackup(params.database);
    return { success: true, backup_id: backupId };
  }
});

server.start(3000);

Register Custom Server

agent-corex mcp register \
  --name "custom-db-mcp" \
  --url "http://localhost:3000"

Verify

agent-corex mcp list
# custom-db-mcp should appear in the list

Server Status & Monitoring

Dashboard View

Go to dashboard.agent-corex.com/servers:

┌─────────────────────────────────────────────────────┐
│ Connected MCP Servers                               │
├─────────────────────────────────────────────────────┤
│                                                     │
│ GitHub                            ✅ CONNECTED     │
│ Status: Healthy                                     │
│ Tools: 25                          Last check: 30s │
│ Uptime: 99.98%                                      │
│                                                     │
│ Slack                             ✅ CONNECTED     │
│ Status: Healthy                                     │
│ Tools: 18                          Last check: 2m  │
│ Uptime: 99.95%                                      │
│                                                     │
│ Jira                              ✅ CONNECTED     │
│ Status: Degraded (2/3 tools working)               │
│ Tools: 22                          Last check: 5m  │
│ Uptime: 98.5%                                       │
│                                                     │
│ Terraform                         ❌ DISCONNECTED  │
│ Status: Error - Invalid token                      │
│ Tools: 0                           Last check: 1h  │
│                                                     │
└─────────────────────────────────────────────────────┘

CLI View

agent-corex mcp status

Troubleshooting

Connection failed - invalid token

Verify token has not expired
Check scopes are correct
Try generating a new token
Re-connect in dashboard

Tools not appearing

Refresh the page or restart CLI
Check “Last synced” time in dashboard
Click “Resync” button manually
Check server status (should be green)

Server showing as disconnected

Click the server card
Go to “Connection Settings”
Re-enter credentials
Click “Test Connection”
If still failing, check your internet connection

Rate limit exceeded

Different services have different rate limits:

GitHub: 5,000 requests/hour
Slack: 2 requests/second
Jira: Varies by plan

Agent-CoreX handles retry logic, but you may need to wait or upgrade your plan.

Best Practices

1. Use Scoped Tokens

# ❌ Bad: Too permissive
Personal Token: "ghp_xxx" (repo, admin, delete)

# ✅ Good: Minimal permissions
Personal Token: "ghp_yyy" (repo, read:user only)

2. Rotate Tokens Regularly

Set reminder to rotate tokens every 90 days

3. Monitor Usage

# Check API usage in dashboard
Dashboard → Servers → GitHub → Usage Stats

4. Test Before Production

# Test in development workspace first
agent-corex workspace create dev
agent-corex mcp connect github  # Dev token
# Test workflows...
# Then connect production token

Integration Examples

GitHub + Slack

const tools = await agent.retrieveTools({
  query: "Create GitHub PR and notify Slack"
});
// Gets both GitHub and Slack tools in one query

Jira + GitHub + Slack

const tools = await agent.retrieveTools({
  query: "Create Jira issue, create GitHub issue, notify team on Slack"
});
// All three servers' tools are available

Custom DB + Slack

const tools = await agent.retrieveTools({
  query: "Backup database and notify admins"
});
// Gets custom-db-mcp tools and Slack tools

Next Steps

MCP Concepts

Understand the Model Context Protocol.

Example: Filesystem MCP

Create your first custom MCP server.

GitHub Automation

Use GitHub MCP for real workflows.

Dashboard

Manage your servers.

Ready to connect? Start with GitHub MCP and try your first automation! 🚀

Getting Started

Core Concepts

MCP Servers

Tool Retrieval System

Use Cases

​Setting Up MCP Servers

​Quick Start: Connect Your First Server

​Step 1: Go to Dashboard

​Step 2: Find a Server

​Step 3: Click “Connect”

​Step 4: Authenticate

​Step 5: Done!

​MCP Servers for Developers: Setup Guide

​GitHub Setup

​Slack Setup

​Jira Setup

​Terraform Setup

​MCP Servers in VS Code

​Install MCP Server Extension

​Connect Servers

​Same authentication as web dashboard

​MCP Servers for Claude Code

​Installation

​Connect Servers

​List Connected Servers

​MCP Servers in Copilot

​Step 1: Enable Integration

​Step 2: Configure

​Step 3: Use in Copilot

​Custom MCP Servers

​Example: Custom Database Tool

​Register Custom Server

​Verify

​Server Status & Monitoring

​Dashboard View

​CLI View

​Troubleshooting

​Best Practices

​1. Use Scoped Tokens

​2. Rotate Tokens Regularly

​3. Monitor Usage

​4. Test Before Production

​Integration Examples

​GitHub + Slack

​Jira + GitHub + Slack

​Custom DB + Slack

​Next Steps

MCP Concepts

Example: Filesystem MCP

GitHub Automation

Dashboard

Setting Up MCP Servers

Quick Start: Connect Your First Server

Step 1: Go to Dashboard

Step 2: Find a Server

Step 3: Click “Connect”

Step 4: Authenticate

Step 5: Done!

MCP Servers for Developers: Setup Guide

GitHub Setup

Slack Setup

Jira Setup

Terraform Setup

MCP Servers in VS Code

Install MCP Server Extension

Connect Servers

Same authentication as web dashboard

MCP Servers for Claude Code

Installation

Connect Servers

List Connected Servers

MCP Servers in Copilot

Step 1: Enable Integration

Step 2: Configure

Step 3: Use in Copilot

Custom MCP Servers

Example: Custom Database Tool

Register Custom Server

Verify

Server Status & Monitoring

Dashboard View

CLI View

Troubleshooting

Best Practices

1. Use Scoped Tokens

2. Rotate Tokens Regularly

3. Monitor Usage

4. Test Before Production

Integration Examples

GitHub + Slack

Jira + GitHub + Slack

Custom DB + Slack

Next Steps