Nextora

co.nextoraPublished by nextora.coOfficial publisherv1.0.0Updated Nov 4, 2026

CRM, projects, ERP, shared inbox, automation and analytics in one business workspace.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for Nextora, a business workspace combining CRM, projects, ERP, shared inbox, automation and analytics.

What you can do
  • The manifest lists no tools, so the exact operations are not documented.
  • Based on the description, the workspace covers CRM, projects, ERP, a shared inbox, automation and analytics.
  • An assistant connected to it would presumably work with business records and workspace data, but the specific actions are unconfirmed.
When to use it
Consider it if your team already runs Nextora as its business workspace and you want an assistant to work with that data. Without a tool list or documentation, verify the available capabilities before relying on it.
Requirements
A remote MCP endpoint at mcp.nextora.co over streamable HTTP. OAuth authentication is required, so a Nextora account with the appropriate workspace access is needed. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to a workspace holding CRM, ERP, inbox and project data, which is likely sensitive business and customer information. The tool list is not published, so what the assistant can read, write, send or delete cannot be confirmed in advance; review the granted scopes carefully.

Installation

In SourceWeft

  1. Open Nextora in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.nextora%2Fnextora/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nextora": {
      "type": "http",
      "url": "https://mcp.nextora.co/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.