"chrome" matching MCP servers:

Enables AI agents to read Jira and Confluence by routing requests through an already logged-in Chrome Atlassian tab, with no API token and read-only access.

An MCP server that lets AI assistants create, search, and manage Jira issues using Chrome browser session cookies for authentication, eliminating the need for API tokens.

Enables AI agents to read and change jobs, job status, customers, quotes with line items, invoices, quote and invoice email, payments, and Scheduler bookings in an account by reusing the user's own signed-in Chrome session, with no official API keys needed. Ships read-only hints and confirmation prompts for tools that reach other people, and can be run over stdio or streamable HTTP.

MCP server that enables accessing Jira and Confluence using browser cookies captured via a Chrome extension, avoiding the need for API tokens or browser automation. It wraps the mcp-atlassian toolset and works with Atlassian Cloud and Server/Data Center behind SSO.

Enables AI agents to read and write a Contractor Foreman account — projects, daily logs, schedules, punchlists, estimates, change orders, invoices, job costing, time cards and more — through 89 tools authenticated with cookies pulled from your own Chrome session. Runs self-hosted on your machine over stdio or HTTP for any MCP client, with matching REST and Python access.

Enables MCP clients to query and modify Jira Server/Data Center and Confluence through a local Chrome login session cookie instead of a token. It includes upstream Jira and Confluence tools, with optional read-only mode to disable writes.