MCP DevTools

Created By
DXHeroesa year ago
MCP DevTools: A suite of Model Context Protocol servers enabling AI assistants to interact with developer tools and services
Overview

What is MCP DevTools?

MCP DevTools is a suite of Model Context Protocol servers that enable AI assistants to interact with developer tools and services seamlessly.

How to use MCP DevTools?

To use MCP DevTools, configure the integration in your Cursor IDE by adding new MCP servers for services like Jira and Linear, and set the required environment variables.

Key features of MCP DevTools?

  • Seamless integration with external services and tools.
  • Extensible framework for creating new integrations.
  • Powerful interactions allowing AI to access and manipulate data.
  • Robust integrations specifically for Jira and Linear.
  • Developer-friendly setup with comprehensive documentation.

Use cases of MCP DevTools?

  1. Automating ticket management in Jira.
  2. Streamlining issue tracking in Linear.
  3. Enhancing productivity through AI-driven commands in development environments.

FAQ from MCP DevTools?

  • Is MCP DevTools free to use?

Yes! MCP DevTools is free to use for everyone.

  • What services can I integrate with MCP DevTools?

Currently, it supports Jira and Linear, with plans for more integrations in the future.

  • What is the current status of MCP DevTools?

The project is in beta, and APIs may change during this phase.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
DXHeroes
Star
2
Language
TypeScript
License
MIT 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