Connections & Capabilities
Connects To
Capabilities
Quickstart
Install
npx -y @smithery/cli install @nguyenvanduocit/all-in-one-model-context-protocol --client claudeConfig
{
"mcpServers": {
"my_mcp_server": {
"command": "all-in-one-model-context-protocol",
"args": ["-env", "/path/to/.env"],
}
}
}Exposed MCP Tools (14)
calendar_create_eventCreates a new event in Google Calendar.
Creates calendar events, potentially spamming users.
calendar_list_eventsLists upcoming events in Google Calendar.
Read-only access to calendar events.
confluence_searchSearches content within Confluence.
Read-only access to Confluence content.
confluence_create_pageCreates a new page in Confluence.
Creates new Confluence pages, potentially cluttering the space.
deepseek_reasoningLeverages Deepseek AI for advanced reasoning tasks.
Relies on external AI service for reasoning.
get_web_contentFetches content from a specified URL.
Read-only access to web content.
gchat_send_messageSends a message to a Google Chat space.
Sends messages to Google Chat, potentially spamming users.
ai_web_searchSearches the web using Google AI Search.
Read-only access to web search results.
gitlab_list_projectsLists GitLab projects within a group.
Read-only access to GitLab project information.
gitlab_create_mrCreates a new merge request in GitLab.
Creates merge requests, potentially triggering CI/CD pipelines.
gmail_searchSearches emails in Gmail.
Read-only access to Gmail emails.
gmail_move_to_spamMoves specific emails to the spam folder in Gmail.
Moves emails to spam, potentially hiding important messages.
jira_get_issueRetrieves detailed information about a specific Jira issue.
Read-only access to Jira issue information.
jira_search_issueSearches for Jira issues using JQL.
Read-only access to Jira issue information.
Safety Assessment
The server offers a wide range of tools, some of which can modify or delete data. Exercise caution when enabling tools with write access and ensure proper secrets management. The `ENABLE_TOOLS` variable provides a degree of control, but careful configuration is essential to minimize risks.
- Granular tool enabling via `ENABLE_TOOLS` environment variable.
- Most tools require specific API keys or tokens, limiting unauthorized access.
- Clear separation of concerns into distinct tool groups (e.g., `gemini`, `gitlab`, `jira`).
- Some tools are read-only, reducing the risk of unintended modifications.
- Many tools have write and delete capabilities, posing a risk of data modification or deletion.
- Reliance on environment variables for secrets management can lead to exposure if not handled carefully.
- Lack of explicit sandboxing for script execution tools.
- Potential for privilege escalation if API keys are compromised.