wals.pro AI 4 weclapp

pro.wals.aiPublished by ai.wals.proOfficial publisherv1.0.0Updated Oct 24, 2026

weclapp ERP in your AI assistant: reads instantly, writes only after a preview you approve.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that connects an AI assistant to weclapp ERP, reading data directly and writing only after a preview you approve.

What you can do
  • Read weclapp ERP data such as records and business objects on demand.
  • Prepare write operations and show a preview before anything is applied.
  • Apply changes to weclapp only after the user approves the preview.
  • Connect through a hosted remote endpoint rather than a local install.
When to use it
Useful when an assistant needs to look up or work with data in a weclapp ERP account, and you want a review step before any change is written back.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no local package or runtime is needed. OAuth authentication is required, so a weclapp account reachable through that sign-in is needed. Network access to the provider's endpoint.
Before you install
The server can write to your weclapp ERP data once a preview is approved, so review each preview carefully before confirming. Sign-in is via OAuth, granting the server access to your weclapp account. Business data is handled by the third-party provider hosting the endpoint.

Installation

In SourceWeft

  1. Open wals.pro AI 4 weclapp 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/pro.wals.ai%2Fweclapp/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": {
    "wals-pro-ai-4-weclapp": {
      "type": "http",
      "url": "https://mcp.ai.wals.pro/v1/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.