connectors

LegalZoom reads contracts and other legal documents you upload, scans for common risk areas, and returns an annotated summary in plain language. It highlights problematic clauses, missing standard protections, and unusual terms, then maps each issue to a RED/YELLOW/GREEN risk level so you know what needs urgent attention versus what is likely safe. The plugin also extracts key metadata — parties, dates, payment terms, renewal windows — so you can compare versions quickly. It generates short explanations for flagged items, suggests negotiation language you can paste into an email, and links each point to relevant law sections or plain-English guides so you can verify the reasoning. When a flagged item requires a licensed attorney, the plugin connects you directly to LegalZoom's network of real lawyers and can open a consult request with the document attached. Developed for people who sign many agreements, it supports PDFs and common text formats, tracks what it reviewed, and keeps a simple history of past scans for reference. The tool reads your inputs locally in the session and returns structured findings you can copy or export. Example: a freelancer receives a long client contract with a problematic indemnity and tight deadlines — LegalZoom flags the indemnity as RED, suggests safer wording, and offers a lawyer consult without switching apps. That saves the back-and-forth of exporting files, drafting notes, and hunting for an attorney before you hit “sign.”

Postman brings the full Postman platform into Claude Code. It connects your Postman account via the MCP Server, syncs collections and environments, and pulls up API schemas and examples. You can browse and import collections, watch for collection updates, and map requests to local files so your code references stay in sync without flipping back to the Postman app. You can generate client code and code snippets in multiple languages from collection requests, export SDKs, and create ready-to-run examples for teammates. The plugin runs collection and integration tests, reports failures with request/response logs, and starts mock servers from examples. It also publishes API documentation and runs security checks against your workspace to flag common misconfigurations or missing auth flows. Use it when you’re coding in Claude Code and need to run a Postman test, generate a TypeScript client, or spin up a mock server without opening a browser. For example, when a backend change breaks an endpoint, you can pull the latest collection, run failing tests, inspect responses, generate a patched client, and push documentation updates — all from the editor, saving context switches and time.

Connect your dev workflow to Atlassian tools and keep working where you already are. Create, update, comment on, transition, and attach files to Jira issues; run JQL and pull lists or single-ticket details; search Confluence pages, fetch page content or page history; and read Compass components and service metadata. It uses OAuth, so it reads and acts with your existing Atlassian permissions instead of bypassing access controls. Use plain language to generate tickets, map labels, and assign owners, or ask for a JQL query and get back structured results you can copy into scripts. Pull Confluence sections into a status report, export ticket lists to CSV, and run bulk updates or scripted transitions. You can also add comments and watchers, create sprint reports, and snapshot backlog views without switching tabs. Imagine preparing a release status: pull the sprint backlog, list blockers by label across projects, fetch the latest Confluence release notes, and create follow-up Jira tasks from a single chat thread. That workflow removes manual copying, reduces tool switching, and saves time during tight ship cycles.

This plugin connects Claude Code to a Sanity MCP server so you can read and write content without jumping between apps. It runs GROQ queries, previews query results inline, and helps you refine queries by pointing out missing projections or suggesting filters. You can pull documents, create or edit records, toggle drafts and published states, and track changes before you send updates back to Sanity. It reads and edits schemas, maps field types, and shows relationships between documents. Visual Editing support lets you edit content in a live page context and then push updates to Sanity. You can generate images through the image pipeline, attach assets to documents, and run basic validation checks on fields and references. The plugin also searches your project docs and example queries so you can borrow patterns quickly. Imagine a marketing lead asking for a copy tweak on a campaign page during standup: you run a GROQ to find the page, edit the rich text in the visual editor, attach an updated image, and publish—all from Claude Code. That saves context switching between IDE, Sanity Studio, and the media library and keeps you in a single workflow for quick fixes and reviews.

Zapier connects Claude Code to over 8,000 apps so you can discover and run automations without writing glue code. It reads your available Zapier apps and actions, lists triggers and fields, and runs chosen actions directly from the conversation. You can search for app actions, map Claude outputs into Zapier fields, and execute create, update, or search operations on third-party services. It handles the OAuth flow through your Zapier account, pulls metadata about action inputs and outputs, and returns structured results you can inspect or pass to further steps. You can run single actions on demand, test mappings with sample data, and view execution responses including IDs and status. The integration also supports trigger polling so you can fetch recent events and act on them inside Claude Code. Imagine drafting an email and having Claude build the contact, log the message in your CRM, and create a follow-up task in your project board without opening Zapier or multiple apps. That saves time when you need to push data across services during a coding session or a planning meeting and prevents constant switching between tools to run or test automations.

Connect Claude Code to your Linear workspace to create, update, and move issues without leaving your editor. The plugin authenticates with Linear, reads your teams and projects, sends new issues with titles, descriptions, labels, assignees, and estimates, and updates existing issues' state and fields. It also pulls issue details and comments so you can reference tickets while coding. You can search across workspaces, filter by sprint, label, or assignee, and open the matching issue in a single command. It watches for status changes you request and runs transitions on the board (e.g., "move to In Progress" or "archive"), and it records links to commits or PRs you paste into an issue. It uses the linear-cli pattern on GitHub to map local commands to API calls, so permissions and rate limits behave like the official client. The plugin handles pagination, resolves user names, and surfaces API errors with actionable messages you can copy into a console for debugging. In practice, you can run a code review and update the ticket state, add the merge link, and assign follow-ups without switching to the Linear web app. That saves time when fixing multiple small bugs during a bug bash or when triaging crash reports during a sprint—no tab switching, fewer context losses.

This plugin connects Claude Code to Asana and exposes core Asana operations as callable actions. It reads projects, lists tasks, pulls task details, creates new tasks, updates fields, adds comments, attaches files by URL, marks tasks complete, and searches by assignee, tag, or custom field. The plugin maps Asana workspace, project, section, and custom field IDs so your code can reference them reliably. It supports pagination when listing large projects and returns structured JSON for tasks, subtasks, and dependencies. You can filter by completion status or due date, sort results, and batch-update multiple tasks. The plugin also watches for recent task activity so you can trigger flows when a task is assigned or a comment appears. Use it to build automation that assigns incoming bug reports to the right project, posts a comment with triage notes, and marks the task in a sprint board without opening Asana. In a daily standup script it saves time by pulling current sprint tasks and statuses so you don’t switch tools to prepare reports. GitHub: https://github.com/anthropics/claude-plugins-official

Connects Claude to your meeting notes and calendar history — surface what was discussed in past meetings and tie it directly to the work at hand.Circleback pulls your meeting notes, transcripts, emails, and calendar straight into Claude Code, so you can search through everything you've discussed and find exactly what you need. Instead of hunting through old messages or trying to remember what happened in that meeting three weeks ago, you can quickly surface action items, recall conversations with specific people or companies, and grab the context you need without leaving your workspace.

Intercom connects your Intercom workspace to Claude Code with read-only OAuth so you can search and inspect conversations from the terminal. It reads conversation threads, pulls contact and company records, and opens the original Intercom URLs so you can jump back to the dashboard when needed. Permissions are limited to reading data only; nothing is written back. Use concrete queries to search by keyword, tag, assignee, and time range. The plugin returns message excerpts, metadata, and contact fields, and it maps conversations to companies and segments. It can list recent conversations for a contact, fetch the last N messages, and surface linked tickets or custom attributes that your team uses in Intercom. It analyzes support patterns by aggregating counts, surfacing frequent topics, and highlighting recurring tags or phrases across conversations. You can pull quick summaries for a ticket set, export a compact customer profile that includes last contact, open issues, and plan tier, and spot whether multiple contacts report the same problem. In practice you can run a search and assemble a customer handoff or bug report without opening the Intercom dashboard: an engineer can gather recent error reports from affected users, a support lead can compile weekly issue trends, and a CSM can build a profile before a call — all without switching tools, saving time and context switches.

Mintlify reads your repo, converts content from Markdown, HTML, or plain files into MDX, and generates ready-to-deploy Mintlify docs. It maps headings, code blocks, frontmatter, and assets into the right MDX components, creates table-of-contents entries, and writes routes and metadata so the site builds predictably. It also validates links and flags missing images or broken references before you publish. You can run it to batch-convert existing docs, or wire it into CI to watch branches and create pull requests that add or update pages. It commits converted files, updates navigation, and can tag changes. It exposes options to customize which components wrap code samples, how props are mapped, and how examples are embedded so the output matches your style guide. Imagine a repo where docs live in mixed formats and engineers are filing PRs just to fix docs. Mintlify reads those files, converts and syncs them into MDX, opens PRs with the changes, and updates the site config. That avoids context-switching between editors and hosting consoles and saves hours on manual conversions during a release.