Daftra Connector (Awsel)

app.awselPublished by awsel.appv1.0.0Updated Oct 29, 2026

Turn chat invoices into drafts in Daftra accounting. 16 tools, OAuth sign-in, human approval.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant turn chat-described invoices into draft entries in the Daftra accounting system, with OAuth sign-in and human approval.

What you can do
  • Create draft invoices in Daftra from invoice details described in chat
  • Work through 16 tools covering the connector's invoice drafting flow
  • Require human approval before drafts are finalized
  • Sign in to the Daftra account through OAuth
When to use it
Useful when you discuss invoice details in chat and want them turned into draft invoices in Daftra without retyping them, while keeping a person in the loop before anything is committed.
Requirements
A remote MCP endpoint (streamable HTTP) at the provider's hosted address; no local package or environment variables. An OAuth sign-in to the Daftra account is required.
Before you install
The server acts on accounting data in your Daftra account, so review drafts before approving them. It relies on OAuth access to that account and sends invoice content to a third-party hosted endpoint; the exact scope of the 16 tools is not documented here.

Installation

In SourceWeft

  1. Open Daftra Connector (Awsel) 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/app.awsel%2Fdaftra/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": {
    "daftra-connector-awsel": {
      "type": "http",
      "url": "https://daftra-connector-saas.onrender.com/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.0LatestOct 29, 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.