Smartdocs Mcp

io.github.jink9428-sourcePublished by GitHub account jink9428-sourcev0.2.1Updated Oct 24, 2026

Korean export docs: agents create invoice & packing list drafts via OAuth.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant draft Korean export documents, specifically invoice and packing list drafts, through an OAuth-protected connection.

What you can do
Create invoice drafts for Korean export shipments through the connected assistant service. Create packing list drafts for the same export workflow. Access is gated by OAuth, so the assistant works within the account that authorizes the connection. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you prepare Korean export paperwork and want an assistant to draft invoices and packing lists instead of typing them from scratch. It fits export or trade workflows where drafts are reviewed before being finalized.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so the user must authorize the connection with the provider's account. No environment variables or headers are declared.
Before you install
The server creates document drafts, so review each draft before using it for real shipments. OAuth grants the server access to your account; check which scopes are requested. Export documents contain commercial and customer data, which is sent to the remote provider.

Installation

In SourceWeft

  1. Open Smartdocs Mcp 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/io.github.jink9428-source%2Fsmartdocs-mcp/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": {
    "smartdocs": {
      "type": "http",
      "url": "https://utumzigtyrxraouoskap.supabase.co/functions/v1/mcp"
    }
  }
}

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

2
  1. v0.2.1LatestSep 29, 2026
  2. v0.2.0Sep 28, 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.