Recur

tw.recurPublished by recur.twOfficial publisherv0.0.1Updated Oct 24, 2026

Subscription payment platform for Taiwan — manage products, customers, and billing

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for Recur, a Taiwan subscription payment platform, letting an assistant manage products, customers, and billing.

What you can do
Recur is a subscription payment platform for Taiwan. Through this remote MCP endpoint, an assistant can work with the platform's core records: products, customers, and billing. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Relevant if you run subscriptions on Recur and want an assistant to help with product, customer, or billing records from a chat session. Not useful if you do not use Recur as your payment platform.
Requirements
A remote endpoint at mcp.recur.tw over streamable HTTP. Authentication is OAuth and is required, so you need a Recur account that can authorize access. No environment variables or headers are declared.
Before you install
This is a payments platform, so an assistant may be able to change products, customer records, or billing, which can affect real charges and subscriber data. The manifest does not list tools, so review what the connected account is allowed to do before granting access. Access is granted through OAuth to a third-party service.

Installation

In SourceWeft

  1. Open Recur 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/tw.recur%2Fmcp/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": {
    "recur": {
      "type": "http",
      "url": "https://mcp.recur.tw/"
    }
  }
}

README

This repository has no README.

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. v0.0.1LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.