EdgeLock Trading Journal

What EdgeLock Trading Journal MCP server does

EdgeLock Trading Journal MCP server connects an AI client with data stored in EdgeLock. Its documented capabilities cover three main areas: retrieving trade information, checking trading statistics, and querying journal content. It also allows a user to add new journal entries through chat.

This makes the server relevant for workflows where an agent needs to inspect existing trading records or capture a new note without switching away from the conversation. The available description does not identify separate tool names, field-level filters, supported markets, or specific journal-entry formats.

How it works

The connection uses the Model Context Protocol to expose EdgeLock-related actions to an AI client. For reading workflows, the agent can request information about trades, statistics, or journal records. For writing workflows, a chat request can be used to log a new journal entry.

OAuth is part of the connection flow, so access is authorized rather than described as an unauthenticated connection. The source material does not explain the OAuth provider, consent steps, token handling, MCP transport, or whether the server runs locally or remotely.

Setup and configuration

The listing states that OAuth is required and that the service is available on a paid plan. Users should therefore have an eligible EdgeLock account and be prepared to complete the service's OAuth authorization flow.

No installation command, configuration file, environment variable, package name, or client-specific setup procedure is provided. The source also does not document a required account tier beyond the statement that a paid plan is needed. Consult EdgeLock's current connection instructions for the actual authorization and client setup steps.

Tools and capabilities

The documented capabilities are:

• Query trades stored in EdgeLock.
• Retrieve trading statistics.
• Query journal content.
• Log new journal entries through chat.

These descriptions indicate read access to trading and journal information plus a write action for new journal entries. They do not establish support for editing or deleting existing entries, importing records, placing trades, generating analytics beyond available statistics, or connecting to other trading platforms.

Limitations and notes

The EdgeLock Trading Journal MCP server's public listing provides only a short capability description; a README is unavailable. As a result, details such as exact tool schemas, request parameters, response formats, error behavior, rate limits, data retention, and audit controls cannot be confirmed.

The listing also does not name supported MCP clients. Compatibility with a particular desktop, editor, or coding client should be verified before deployment. OAuth and the paid-plan requirement are the only stated access conditions. The server is a fit for conversational querying and journal capture in EdgeLock, but the available material is not sufficient to evaluate broader portfolio-management or execution workflows.