Text2Event

com.text2eventPublished by text2event.comOfficial publisherv1.0.0Updated Oct 24, 2026

Extracts calendar events from natural-language text, with .ics and calendar links.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Extracts calendar events from natural-language text and returns .ics files and calendar links.

What you can do
Text2Event turns free-form natural-language text into calendar events. According to the registry description, it returns .ics files and calendar links for the events it extracts. It is a remote MCP server reached over streamable HTTP, so the assistant connects to a hosted endpoint rather than running anything locally.
When to use it
Useful when an assistant needs to turn unstructured text, such as a message or note, into calendar-ready events without the user filling in a form.
Requirements
A remote MCP endpoint at mcp.text2event.com over streamable HTTP. OAuth authentication is required, so the user needs an account with the provider and must complete the OAuth sign-in. No environment variables or headers are declared.
Before you install
Access is granted through OAuth, so the assistant acts with the permissions of the signed-in account. The text sent for extraction goes to a third-party hosted service, so avoid submitting sensitive content. Review extracted events before adding them to a real calendar.

Installation

In SourceWeft

  1. Open Text2Event 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.text2event%2Fmcp/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": {
    "text2event": {
      "type": "http",
      "url": "https://mcp.text2event.com/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 16, 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.