Motaword Mcp

io.github.oytuntezPublished by GitHub account oytuntezv1.0.0Updated Oct 24, 2026

MotaWord MCP Server for professional and certified translations and localization

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant connect to MotaWord for professional and certified translation and localization.

What you can do
This server connects an assistant to MotaWord over a remote endpoint for professional and certified translation and localization. The input states only that purpose and lists no tools or specific operations, so the exact capabilities cannot be confirmed.
When to use it
Use it when you want an assistant to help with professional or certified translation and localization work through MotaWord. It is less relevant for ordinary text translation that does not need a professional or certified process.
Requirements
Requires a connection to the remote endpoint and OAuth authorization. No environment variables or extra headers are declared. Network access is needed.
Before you install
Access to a MotaWord account is granted through OAuth, so the assistant may reach account data or perform actions related to translation projects. The input does not describe the actual permissions or whether data is written, sent, or deleted, so confirm the authorization scope before installing.

Installation

In SourceWeft

  1. Open Motaword 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.oytuntez%2Fmotaword-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": {
    "motaword": {
      "type": "http",
      "url": "https://api.motaword.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.0LatestSep 16, 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.