Roleora

com.roleoraPublished by roleora.comOfficial publisherv1.0.0Updated Oct 24, 2026

Log, search and summarise your work history in Roleora, the career record for professionals.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant log, search and summarise your work history in Roleora, a career record service for professionals.

What you can do
Roleora is a remote MCP server that connects an assistant to your Roleora career record. Based on the description, it lets the assistant add entries to your work history, search that history, and produce summaries of it. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful if you keep a running record of your professional work in Roleora and want an assistant to add to it, look things up in it, or summarise it without switching apps. Less relevant if you do not already use Roleora.
Requirements
A remote server reached over streamable HTTP at the provider's endpoint. Authentication is OAuth and is required, so you need a Roleora account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can write to your career record and read from it, so check what the assistant adds or changes before relying on it. Access is granted through OAuth to your Roleora account; review the permissions requested during sign-in and revoke access if you stop using it.

Installation

In SourceWeft

  1. Open Roleora 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/com.roleora%2Froleora/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": {
    "roleora": {
      "type": "http",
      "url": "https://mcp.roleora.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.