OrgLines

com.orglinesPublished by orglines.comOfficial publisherv1.0.0Updated Nov 7, 2026

Your OrgLines workspace in AI: leads, tasks, notes, mail, invoices. Changes wait for your OK.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that connects an AI assistant to an OrgLines workspace covering leads, tasks, notes, mail and invoices, with changes awaiting your approval.

What you can do
  • Work with leads and invoices in the OrgLines workspace
  • Manage tasks and notes
  • Access mail held in the workspace
  • Propose changes that wait for your confirmation before taking effect
When to use it
Useful if your team runs leads, invoices, tasks, notes and mail in OrgLines and you want an assistant to read and act on that workspace from a chat client, with a human approving any change.
Requirements
A remote endpoint at mcp.orglines.com using streamable HTTP; an OrgLines account signed in through OAuth. No environment variables or headers are declared.
Before you install
The server can change workspace data such as leads, tasks, notes and invoices; the description says changes wait for your approval, so check each confirmation prompt before accepting. It reaches business records and mail held in OrgLines, which are sent to the AI client you connect.

Installation

In SourceWeft

  1. Open OrgLines 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/com.orglines%2Forglines/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": {
    "orglines": {
      "type": "http",
      "url": "https://mcp.orglines.com/api/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 7, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.