Shaka

rw.shakaPublished by shaka.rwOfficial publisherv1.0.0Updated Oct 24, 2026

Company email for Rwanda. Read and send mail from a Shaka mailbox over OAuth or an API key.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Shaka connects an assistant to a Shaka company mailbox for Rwanda, letting it read and send email over OAuth or an API key.

What you can do
Read mail from a Shaka mailbox, including messages and their contents, as described for the service. Send mail from the Shaka mailbox. Connect to the hosted Shaka mail endpoint, authenticated with OAuth or an API key. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to work with a Shaka company mailbox hosted in Rwanda, for example to review incoming messages or send replies on behalf of the account. Only relevant if your organization already uses Shaka for email.
Requirements
A remote MCP endpoint at mail.shaka.rw reached over streamable HTTP. A Shaka mailbox account and OAuth authorization (declared as required) or an API key. No environment variables or headers are declared in the manifest.
Before you install
The server can send mail from your mailbox, so messages may go to real recipients under your identity. It requests OAuth access or an API key, which grants access to your mailbox; treat the credential as sensitive. Mail content is handled by a third-party provider.

Installation

In SourceWeft

  1. Open Shaka 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/rw.shaka%2Fmail/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": {
    "shaka": {
      "type": "http",
      "url": "https://mail.shaka.rw/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

1
  1. v1.0.0LatestSep 19, 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.