Frequently Asked Questions about @kazuph/mcp-devin

Q: What is the purpose of the @kazuph/mcp-devin MCP server? A: The @kazuph/mcp-devin MCP server integrates Devin AI with Slack, enabling automated task posting, contextual thread management, and enhanced session management.

Q: What is MCP? A: MCP stands for Model Context Protocol. It’s an open protocol that standardizes how applications provide context to Large Language Models (LLMs).

Q: What are the key features of @kazuph/mcp-devin? A: Key features include Slack integration (automated task notifications, threaded communication, secure authentication) and core tools for managing Devin sessions (create_devin_session, send_message_to_session, get_devin_session, list_devin_sessions).

Q: What environment variables are required to configure the server? A: The required environment variables are: DEVIN_API_KEY, DEVIN_ORG_NAME (optional), DEVIN_BASE_URL (optional), SLACK_BOT_TOKEN, and SLACK_DEFAULT_CHANNEL.

Q: How do I integrate @kazuph/mcp-devin with Claude Desktop? A: You can integrate it by adding the server configuration to the claude_desktop_config.json file in the appropriate directory for your operating system (MacOS or Windows).

Q: How can I debug the @kazuph/mcp-devin server? A: You can use the MCP Inspector for debugging. Run pnpm run inspector to access debugging tools in your browser.

Q: Can I use channel names (e.g., #general) instead of channel IDs for SLACK_DEFAULT_CHANNEL? A: Yes, you can use either the channel ID (e.g., C123ABC456) or the channel name (e.g., general or #general) for the SLACK_DEFAULT_CHANNEL environment variable.

Q: How does UBOS enhance the capabilities of @kazuph/mcp-devin? A: UBOS provides a full-stack AI Agent Development Platform that enables multi-agent orchestration, enterprise data integration, custom AI agent development, and centralized management and monitoring, complementing the Slack integration provided by @kazuph/mcp-devin.

Q: What are some use cases for @kazuph/mcp-devin? A: Some use cases include automated code generation, bug fixing and resolution, automated testing, project management and collaboration, and documentation generation.

Q: Where can I find the MCP Inspector for debugging? A: The MCP Inspector is available at https://github.com/modelcontextprotocol/inspector.