ORYKSA AI Employees

com.oryksaPublished by oryksa.comOfficial publisherv1.1.0Updated Oct 24, 2026

AI support employee for any website: learns the site, answers visitors by chat and voice.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant answer website visitors' questions by chat and voice, learning from the site.

What you can do
This remote service provides a website support assistant that learns the site and answers visitor questions through chat and voice. The tool list is not published in the manifest, so the exact operations available should be confirmed from the provider's documentation.
When to use it
Relevant when a website needs a support or guided assistant that answers visitor questions from the site's own content, with both chat and voice interaction.
Requirements
Requires a connection to the remote endpoint at mcp.oryksa.com and OAuth authorization. No environment variables or custom headers are declared.
Before you install
Access is granted through OAuth, so review the scopes and which site data the assistant can reach. Visitor conversations are handled by the service and may be sent to a third party; confirm its data handling before connecting.

Installation

In SourceWeft

  1. Open ORYKSA AI Employees 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.oryksa%2Fai-employees/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": {
    "oryksa-ai-employees": {
      "type": "http",
      "url": "https://mcp.oryksa.com/"
    }
  }
}

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.1.0LatestSep 23, 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.