Studex MCP Server

io.github.itshivamsPublished by GitHub account itshivamsv1.0.0Updated Oct 24, 2026

Model Context Protocol server for Studex tools, notifications, and profile integrations

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that connects an assistant to Studex tools, notifications and profile integrations through an OAuth-protected endpoint.

What you can do
Access Studex tools exposed by the server, as described in the registry listing, though no individual tools are enumerated in the available material. Work with notifications through the connected Studex account. Use profile integrations tied to the same account. Because no tool list, instructions or README were supplied, the exact operations available cannot be confirmed from this entry.
When to use it
Consider it when you already use Studex and want an assistant to reach its tools, notifications and profile integrations from a chat client that supports remote MCP servers with OAuth.
Requirements
A remote MCP endpoint at studex.club reached over streamable HTTP. OAuth authentication is required, so a Studex account and a client that can complete the OAuth flow are needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Studex account, so review the scopes requested during authorization. The server may read or change notifications and profile data, but the specific write actions are not documented here. No tool list or README is available to confirm what data is sent to third parties.

Installation

In SourceWeft

  1. Open Studex MCP Server 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.itshivams%2Fstudex-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": {
    "studex": {
      "type": "http",
      "url": "https://studex.club/api/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.