MCP Jira Stdio vs Sheets MCP

A side-by-side look at the MCP Jira Stdio and Sheets MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP Jira Stdio logoMCP Jira StdioWorkplace & Productivity · Local subprocess (stdio)MCP server for Jira Cloud — issues, search, comments, attachments, transitions.65GreatAuth: not declaredSheets MCP logoSheets MCPWorkplace & Productivity · Local subprocess (stdio)Google Sheets for agent workflows in Claude Code and Claude Desktop: APIs, files, schedules, undo.68GreatAuth: oauth 2.0

Verdict: choose MCP Jira Stdio for workplace & productivity work as a local process; choose Sheets MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP Jira Stdio logoChoose MCP Jira Stdio when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: JIRA_BASE_URL, JIRA_EMAIL, JIRA_API_TOKEN.
  • You want tools like jira_get_visible_projects, jira_get_issue, jira_search_issues.
Explore MCP Jira Stdio

Sheets MCP logoChoose Sheets MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like google_accounts, find_spreadsheet, create_spreadsheet.
Explore Sheets MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Jira Stdio logoMCP Jira StdioSheets MCP logoSheets MCP
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal65/100 · Great68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredFree
Required env varsJIRA_BASE_URLJIRA_EMAILJIRA_API_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1435
Directory activity 0 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools2329

Tools & capabilities

MCP Jira Stdio tools 23

  • jira_get_visible_projectsRetrieves all projects accessible to the authenticated user. Returns project keys, names, descriptions, and basic metadata.
  • jira_get_issueRetrieve details for a specific Jira issue by key or URL. Use this when the user mentions an issue like "PAYWALL-943" or pastes a Jira link (e.g., https://your.atlassian.net/browse/PAYWALL-943). Returns status, assignee, priority, project, type, labels, components, timestamps, and description.
  • jira_search_issuesSearch for Jira issues using JQL. Supports complex queries with pagination and field selection. Examples: "project = PROJECT AND status = Open", "assignee = currentUser()". For pagination, use nextPageToken from previous response.
  • jira_get_my_issuesRetrieves issues assigned to current user, sorted by most recently updated first. Supports pagination and field selection. For pagination, use nextPageToken from previous response.
  • jira_get_issue_typesRetrieves available issue types. Can get global issue types or project-specific issue types including regular issues and subtasks (Bug, Story, Task, Epic, etc.).
  • jira_get_usersSearch for users by name, email, username, or account ID. Returns display name, email, account status, and account type. Supports pagination.
  • jira_get_prioritiesRetrieves available priorities (e.g., Highest, High, Medium, Low, Lowest). Returns IDs, names, and descriptions.
  • jira_get_statusesRetrieves available statuses (global or project-specific, e.g., To Do, In Progress, Done). Returns status categories and workflow information.
  • jira_get_project_infoRetrieves detailed information about a project (components, versions, issue types, roles, insights). More comprehensive than the basic project list.
  • jira_get_create_metaRetrieves create metadata for a project, showing all available fields (including custom fields) for creating issues. Shows required vs optional fields, field types, and allowed values. Use this before creating issues to discover what fields are needed.
  • jira_get_custom_fieldsRetrieves all custom fields available in Jira. Shows custom field names, IDs (e.g., customfield_10071), and types. Useful for discovering what custom fields exist and their identifiers.
  • jira_get_commentsRetrieves all comments for a Jira issue. Returns comment author, content, timestamps, and visibility settings. Supports pagination for issues with many comments.
  • +11 more on the listing page

Sheets MCP tools 29

  • google_accountsManage the Google accounts Sheets MCP can use. list: show signed-in accounts and the default. add: sign in to a Google account (opens a browser sign-in; also use this when a sign-in has expired). remove: sign an account out and revoke access. set_default: choose the account used for new spreadsheets.
  • find_spreadsheetFind a spreadsheet by name among the ones the user has opened or created with Sheets MCP before (the list is kept on their computer). Use it when the user names a sheet instead of pasting a link, e.g. "my budget sheet". It can't search the rest of their Google Drive: if nothing matches, ask for the link. Leave query empty to list the most recent.
  • create_spreadsheetCreate a new Google Sheets spreadsheet.
  • get_spreadsheet_infoGet a spreadsheet's title, tabs (sizes, frozen rows/cols), charts (ids, types, data ranges), named ranges, and the first few rows of each tab. Call this first to understand a sheet's layout.
  • read_rangeRead cell contents from a range, or its formatting with mode "formats". Large ranges are truncated; use next_range to continue.
  • read_rangesRead several ranges in one call, across any tabs. Faster than calling read_range repeatedly. Each range is truncated to its share of max_cells; use its next_range with read_range to continue.
  • write_rangeWrite values and/or formulas starting at the top-left cell of the range. Input is parsed like typing into the UI (formulas, dates, percentages work). Previous contents are saved for undo_last. Returns any formula errors found after writing.
  • fill_rangeFill cells from a source block, like dragging the fill handle or pasting onto a bigger selection: the source's formulas (relative references shift), values and formatting repeat across the destination. Use it after writing one row or column of formulas to extend them across a table, instead of sending every column. With continue_series, patterns continue instead (1, 2, 3 → 4, 5, 6; Jan → Feb; dates). The destination's previous contents are saved for undo_last. Returns any formula errors found after filling.
  • append_rowsAppend rows after the last row of data in a table (detected from the given range or tab).
  • clear_rangeClear values and formulas in a range (formatting is kept). Previous contents are saved for undo_last.
  • find_replaceFind and replace text across a tab or the whole spreadsheet. Not undoable - consider read_range first.
  • undo_lastUndo the most recent write_range, append_rows, or clear_range made through this server (restores values/formulas only, not formatting or structure). History is kept in memory until the server restarts.
  • +17 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP Jira Stdio

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-jira-stdio": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-jira-stdio@latest"
      ],
      "env": {
        "JIRA_BASE_URL": "YOUR_JIRA_BASE_URL_HERE",
        "JIRA_EMAIL": "YOUR_JIRA_EMAIL_HERE",
        "JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE"
      }
    }
  }
}

Sheets MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sheets-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@sheetsmcp/server"
      ]
    }
  }
}

Frequently asked questions

MCP Jira Stdio is categorized under Workplace & Productivity and uses a local stdio subprocess. Sheets MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick MCP Jira Stdio for workplace & productivity work and Sheets MCP for workplace & productivity.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP Jira Stdio has no declared pricing — check the project's own site. Sheets MCP is listed as free. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-jira-stdio and sheets-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Jira Stdio has a quality signal of 65/100 (Great) with 0 views, 0 installs and 14 GitHub stars. Sheets MCP has 68/100 (Great) with 8 views, 0 installs and 35 GitHub stars.