AIO MCP Server

Created By
athaponga year ago
A powerful Model Context Protocol (MCP) server implementation with integrations for GitLab, Jira, Confluence, YouTube, and more. This server provides AI-powered search capabilities and various utility tools for development workflows.
Overview

What is AIO-MCP Server?

AIO-MCP Server is a powerful Model Context Protocol (MCP) server implementation that integrates with various platforms like GitLab, Jira, Confluence, and YouTube, providing AI-powered search capabilities and utility tools for development workflows.

How to use AIO-MCP Server?

To use the AIO-MCP Server, install it via Go by setting up your environment variables and running the installation command. After installation, configure the server by creating a .env file with the necessary API keys and tokens for the services you want to use.

Key features of AIO-MCP Server?

  • Integration with multiple platforms (GitLab, Jira, Confluence, YouTube)
  • AI-powered search capabilities
  • Support for standard input/output and Server-Sent Events (SSE) mode for real-time communication
  • Various utility tools for development workflows

Use cases of AIO-MCP Server?

  1. Automating project management tasks in Jira and GitLab.
  2. Enhancing documentation and collaboration through Confluence.
  3. Fetching and managing content from YouTube.
  4. Utilizing AI for advanced search and data retrieval across integrated platforms.

FAQ from AIO-MCP Server?

  • What programming language is AIO-MCP Server built with?

AIO-MCP Server is built using Go.

  • Is there a cost associated with using AIO-MCP Server?

AIO-MCP Server is open-source and free to use.

  • Can I customize the server's functionality?

Yes! You can enable or disable various tools and customize the server's configuration through environment variables.

Server Config

{
  "mcpServers": {
    "aio-mcp": {
      "command": "<path>/<to>/aio-mcp",
      "env": {
        "ENABLE_TOOLS": "",
        "QDRANT_HOST": "",
        "QDRANT_PORT": "",
        "QDRANT_API_KEY": "",
        "ATLASSIAN_HOST": "",
        "ATLASSIAN_EMAIL": "",
        "ATLASSIAN_TOKEN": "",
        "GITLAB_HOST": "https://gitlab.com",
        "GITLAB_TOKEN": "glpat-",
        "BRAVE_API_KEY": "",
        "GOOGLE_AI_API_KEY": "",
        "PROXY_URL": "",
        "OPENAI_API_KEY": "",
        "OPENAI_BASE_URL": "",
        "OPENAI_EMBEDDING_MODEL": "",
        "GOOGLE_TOKEN_FILE": "<path>/<to>/google-token.json",
        "GOOGLE_CREDENTIALS_FILE": "<path>/<to>/google-credentials.json",
        "GOOGLE_MAPS_API_KEY": "",
        "DEEPSEEK_API_KEY": "",
        "USE_OLLAMA_DEEPSEEK": "",
        "USE_OPENROUTER": "",
        "OPENROUTER_API_KEY": ""
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
athapong
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago