"How to Create Projects in Jira" matching MCP tools:

• projectA

  Done BearA

  Create or change a project. `action: "add"` creates one (name required). `action: "edit"` updates the named project: only the fields given change, and an empty string clears description or target_date. `action: "join"` puts it in the caller's Your projects sidebar list and `action: "leave"` takes it out. Read projects with get_context.

  Connector

  Destructive

  No auth

• projectA

  Done Bear MCPA

  Create or change a project. `action: "add"` creates one (name required). `action: "edit"` updates the named project: only the fields given change, and an empty string clears description or target_date. `action: "join"` puts it in the caller's Your projects sidebar list and `action: "leave"` takes it out. Read projects with get_context.

  Connector

  Destructive

  No auth

• list_projectsA

  LoadsterA

  List the Loadster projects the current token can access, each with its id and name. Every other tool takes one of these ids. An empty list means the connected team has no projects yet: nothing on this surface creates one, so ask the user to create a project in the Dashboard, then call this again.

  ConnectorOAuth

• how-toA

  Fast.ioA

  Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.

  ConnectorNo auth

• build_whoamiA

  SuperoB

  Resolve your API key's scope: role (domain_admin/project_admin), domain, whether you can create projects, and your plan. Call this to decide the flow.

  ConnectorNo auth

• create-projectA

  mcpA

  Create a new project on sota.io. Each project automatically provisions: (1) a managed PostgreSQL 17 database accessible via the DATABASE_URL environment variable (auto-injected, no configuration needed), (2) PgBouncer connection pooling (pool size 20, max 100 clients), (3) automatic daily database backups with 7-day retention, (4) a live URL at https://{slug}.sota.io with automatic HTTPS via Let's Encrypt. The project slug is auto-generated from the name (lowercase, hyphens, max 63 chars) and is immutable after creation. Supported frameworks: Next.js, Node.js (Express/Fastify/Koa), Python (Flask/FastAPI/Django), or any language via custom Dockerfile. You can also add up to 5 custom domains per project with automatic HTTPS (via API: POST /v1/projects/:id/domains with {domain: "yourdomain.com"}). DNS: A record to 23.88.45.28 for apex domains, CNAME to {slug}.sota.io for subdomains. Optionally associate the project with a public git repository at create-time by passing `git_url` (and optional `git_branch`). The association is informational — it shows up in the dashboard and the `sota deploy --git` CLI flag can default to it — but does NOT enable auto-deploy-on-push yet.

  ConnectorNo auth

• list_projectsA

  RoutebaseA

  List all projects in the active organization. Use this to browse projects or find a project id; for one project in full use get_project. Requires organization context (call set_context first).

  ConnectorAPI key

• create_standalone_projectA

  mFlowA

  Create a new standalone project, seeded with default To Do/In Progress/Done statuses. Use this to start tracking work that has no external tracker — for work already in Jira or Trello, use that provider's own tools instead.

  ConnectorOAuth

• list_projectsA

  Cherry NotesA

  Returns all of the user's projects. ONLY call this when the user explicitly asks to see all projects or wants to switch projects — NOT when they say "show me the list" (that means get_items). Show the `display` field to the user verbatim in a code block. If has_more is true, call again with cursor to get more.

  ConnectorOAuth

• search_githubA

  developer-tools-mcp-serverA

  Search GitHub repositories by keyword to discover code, projects, and libraries. Returns matching repositories with star count, description, language, and URL. Use for finding libraries, examples, or competitive projects in specific domains.

  ConnectorNo auth

• search_githubA

  Developer Tools MCP ServerA

  Search GitHub repositories by keyword to discover code, projects, and libraries. Returns matching repositories with star count, description, language, and URL. Use for finding libraries, examples, or competitive projects in specific domains.

  ConnectorNo auth

• list_omnifocus_foldersA

  local-mcpA

  Lists folders in OmniFocus. Folders group related projects (e.g. "Work", "Personal"). Use list_omnifocus_projects to see the projects inside them.

  ConnectorOAuth

• getBuckyMcpGuideA

  BuckyA

  Return what this session should do next. Call it with no arguments on first contact. With no token: the tools that work now (including a free site preview), and how to start OAuth by calling a gated tool. Signed in with no projects: three onboarding questions, not the tool catalogue — answer them by calling this tool again with role, market and scale, and it returns one workflow to run. Signed in with projects: the most recent projects and one next call derived from this account's own incompleteness (unresolved geography, missing analysis, or missing report), falling back to getProjectContext when nothing is unfinished. The anonymous path makes no database call. A signed-in call reads this account's project membership and incompleteness flags only — no geocoder, model, third-party API, PostHog, or meter.

  ConnectorNo auth

• vivu_list_projectsA

  VivuA

  List the video projects available to the signed-in user.

  ConnectorOAuth

• jira_list_projectsA

  JiraA

  List all accessible Jira projects. Returns project keys, names, descriptions, and types. Use before searching to discover available projects.

  ConnectorNo auth

• get_instanceA

  mcpA

  Get information about an instance. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "name": "projects/my-project/instances/my-instance" }

  ConnectorNo auth

• list_projectsA

  ContextLayerA

  List projects in your organization. No parameters needed — just call it to see all your projects.

  ConnectorNo auth

• list_tablesA

  mcpA

  List all tables in a specified instance. The request requires the 'parent' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "parent": "projects/my-project/instances/my-instance" }

  ConnectorNo auth

• create_channelA

  framesailA

  Create a new channel — the container for projects and their reusable styles. Use when the user wants a fresh creative identity rather than adding to an existing channel.

  ConnectorNo auth

• projects_editA

  ZernoteB

  Create or rename projects. action=create needs name; action=rename needs id and name. Delete is not supported yet.

  ConnectorOAuth

• create_branchA

  TolgeeA

  Create a new branch in a Tolgee project by forking from an existing branch. Only available for projects with branching enabled (enterprise feature).

  ConnectorNo auth