Dida365 MCP Server logo

Dida365 MCP Server

by DCjanus

This is an MCP Server implementation for Dida365 using the Dida365 Official API. It provides a standard interface for interacting with Dida365 tasks.

View on GitHub

Last updated: N/A

Dida365 MCP Server

English | 简体中文

This is a MCP Server implementation for Dida365 using the Dida365 Official API.

✨ Features

  • 🔐 Official OAuth 2.0 authentication mechanism
  • 🎯 Standard MCP Server interface
  • 💻 STDIO-based MCP Server implementation

📖 Usage Guide

1. Obtain Access Token

Dida365 uses OAuth 2.0 authorization mechanism to manage API access. You can obtain an access token through either of the following methods:

Option 1: Using Online Service (Recommended)
  1. Visit https://dida365.dcjanus.com/oauth/login in your browser
  2. The system will automatically redirect you to the Dida365 authorization page
  3. Confirm the authorization on the Dida365 page
  4. After successful authorization, you'll be redirected back to the /oauth/callback endpoint
  5. You will receive a JSON response containing the access_token - store it securely
Option 2: Local Deployment
  1. Visit Dida365's Developer Center to create a new application
  2. In the application settings, configure the Redirect URL as http://localhost:8080/oauth/callback
  3. Start the local server (default port: 8080)
  4. Visit http://localhost:8080/oauth/login
  5. Follow the on-screen instructions to complete the authorization process
  6. Obtain the access token

2. Configure MCP Server

Add the following to your configuration file:

{
    "mcpServers": {
        "dida365": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "--init",
                "--pull",
                "always",
                "ghcr.io/dcjanus/dida365-mcp-server:latest",
                "dida365-mcp-server",
                "-access_token",
                "<YOUR_ACCESS_TOKEN>"
            ]
        }
    }
}

Replace <YOUR_ACCESS_TOKEN> with the access token you obtained.

⚠️ Important Notes

  • Keep your access token secure and never share it with others
  • If authorization fails, check your network connection or try reauthorizing