all-in-one-model-context-protocol

MyMCP Server (MyMCP) is designed to provide a centralized Model Context Protocol (MCP) server with integration points to a range of tools and services such as Atlassian products, Google services, GitLab, YouTube, Confluence, Jira, and more. It exposes capabilities for knowledge retrieval, automation, and tooling within AI workflows. With the available tools, you can perform calendar operations, fetch web content, search knowledge bases, interact with project management and collaboration suites, and run script-based utilities. To run the server, configure your environment via a .env file and start the MCP server process; the server will load your tool integrations and expose the MCP endpoints for your AI agent or client to query. This setup enables seamless, context-rich queries to access calendars, Confluence pages, Jira issues, GitLab projects, and other connected services from within prompts and workflows.

Prerequisites:

• Go 1.23.2 or higher installed on your system
• Access to the internet to install modules and dependencies

Installation steps:

1. Install the server via Go:

go install github.com/nguyenvanduocit/all-in-one-model-context-protocol@latest

2. Create a .env file with your configuration (example placeholders shown):

ENABLE_TOOLS=
QDRANT_HOST=
ATLASSIAN_HOST=
ATLASSIAN_EMAIL=
GITLAB_HOST=
GITLAB_TOKEN=
BRAVE_API_KEY=
ATLASSIAN_TOKEN=
GOOGLE_AI_API_KEY=
PROXY_URL=
OPENAI_API_KEY=
DEEPSEEK_API_KEY=
QDRANT_PORT=
GOOGLE_TOKEN_FILE=
GOOGLE_CREDENTIALS_FILE=
QDRANT_API_KEY=

3. Run or configure the MCP server in your client config (see below for example):

{
  "mcpServers": {
    "my_mcp_server": {
      "command": "all-in-one-model-context-protocol",
      "args": ["-env", "/path/to/.env"]
    }
  }
}

Optional: If you prefer, you can also install via Smithery (interactive CLI) as shown in the project notes, but the official Go route is provided above.

Tips:

• The ENABLE_TOOLS environment variable controls which tool groups are active. If left empty, all tools enabled by default.
• Ensure your .env file paths are correct and accessible by the MCP process.
• Some integrations (e.g., Google or Atlassian) require API keys or service account credentials; ensure these are generated in the respective console and pointed to by GOOGLE_TOKEN_FILE, GOOGLE_CREDENTIALS_FILE, and ATLASSIAN_TOKEN.
• For Google-related features, Google Credentials and Tokens may be sensitive; restrict file access and rotate keys periodically.
• If you encounter connectivity issues to external services, verify PROXY_URL settings and network egress permissions.
• When updating dependencies, re-check that your environment variable names match the updated tool integrations.