User guide

How to organise your work in projects, run applications, follow what they cost and connect your AI assistant to Mewiso.

Getting started

Once signed in, the home page shows your credits, your favourites, your latest projects and the applications you can run. The header gives access to the rest of the platform:

  • Projects and Applications, the two main sections described below;
  • Data, the catalogue of maps, dashboards, GeoStories, datasets and documents. Upload your own files (Shapefile, GeoPackage, GeoJSON, GeoTIFF…) from the catalogue;
  • the search field, which finds projects, applications and data by name;
  • your account menu: My runs, My schedules, Team and Subscription.

Click the star of a project, a map or a dataset to add it to your favourites: it then appears on the home page.

Projects

A project gathers the resources of a study (maps, dashboards, GeoStories, datasets, documents) on a single page. It holds links to resources: adding a resource to a project does not copy it, and removing it from the project does not delete it.

Create a project

  1. Click New project on the home page or on the Projects page.
  2. Give it a title and, optionally, a description and a thumbnail (an image of 1 MB at most).
  3. Click Create: the project page opens.

Add resources

On the project page, click Add resources, search the catalogue, filter by type, tick the resources and confirm with Add. Resources are shown in rows by type. The menu of each card lets you Set as welcome, which shows the resource in large at the top of the project, or Remove from project.

To add a new file, upload it to the catalogue first (Data menu), then add it to the project.

Who sees a project

Projects and resources belong to your organisation. Every member of your team can see and download them; managers can also edit and delete them. Nothing is visible to other organisations.

Applications and runs

An application is a processing chain (models, Earth observation analyses…) that you run on your own parameters: an area, a period, datasets. The Applications page lists the applications available to you. Each application page describes it, shows its fees and your recent runs.

Run an application

  1. Parameters: click Run on the application page and fill in the form. Draw or paste (GeoJSON) the area on the map, pick datasets from the catalogue or upload a file. The run name is prefilled as application-date-time and can be changed.
  2. Review: check the parameters, the cost of the run and your available credits, then click Start. Back returns to the form.
  3. Processing: the page updates by itself while the application runs. Stop cancels the run and refunds its credits.
  4. Result: open the output resources (maps, datasets, documents) or click Run again to start from the same parameters.

Output resources are saved in the catalogue, like your other data: add them to a project to keep your study in one place.

Run statuses

Created
Draft waiting for review: nothing is charged yet.
Queued
Started and waiting for a free worker. Credits are charged at this point.
Running
The application is processing your data.
Finished
The run succeeded; its outputs are available.
Failed
The run stopped on an error or was stopped. Its credits are refunded.

My runs lists your runs and filters them by status or application. Team managers see the runs of the whole team.

Cost of a run

Runs are paid in credits. The fees of an application are shown in its Fees card and add up:

Instantiation fee
a fixed amount for each run;
Execution fee
a fixed processing amount for each run;
Per feature
multiplied by the number of resources selected in the form;
Per m²
multiplied by the area of the drawn zone;
Per day
multiplied by the number of days of the period, first and last days included.

The total is rounded up to the next whole credit. Use Estimate a run on the application page to simulate a cost before filling in the form; the exact cost is shown on the review step.

  • Credits are charged when you click Start, not when the draft is created.
  • A failed or stopped run is refunded in full. A finished run is not refunded.
  • If you do not have enough credits, the review step warns you and the run stays a draft: nothing is charged.

Credits and subscription

Credits come from two sources, both shown on your Subscription page:

  • Monthly credits, included in your plan and renewed at the start of each calendar month. Unused monthly credits are not carried over;
  • Extra credits, bought as credit packs. They do not expire at the end of the month.

A run uses monthly credits first, then extra credits, oldest packs first. The Subscription page also shows your plan, its end date, your pending orders and the history of credit usage (with a link to each run) and purchases.

Buy credits or subscribe

  1. On the Subscription page, click Buy credits (or Subscribe if you have no active plan).
  2. Choose the quantity of each pack and click Add to cart.
  3. In the cart, click Validate cart. Your order is sent to our team, who contact you; the credits are added once the order is processed.

Not a customer yet? See the plans and prices and send us the contact form.

Scheduled runs

Some applications can be run periodically, for example to monitor an area every week. A schedule replays the same parameters at a regular interval.

Schedule a run

  1. Fill in the application form as for a single run and go to the review step.
  2. Below Start, open Schedule. This panel only appears for applications that can be scheduled.
  3. Name the schedule, choose how often it repeats (Daily, Weekly, Monthly or Every X months) and the date and time of the first run. The first run sets the time, the weekday and the day of the month of the next ones; on the 31st, shorter months run on their last day.
  4. Click Create schedule. The first run takes place at the chosen date, not immediately.

Manage your schedules

My schedules lists each schedule with its next and last run. From its menu you can Skip next run, Disable or Enable it, Edit its name and frequency, see the Runs of this schedule or Delete it (past runs are kept). To change the parameters, create a new schedule from a new run.

What a schedule costs

  • Each scheduled run is an ordinary run: its cost is computed from the saved parameters and charged when it starts. A schedule costs nothing while no run starts.
  • Count the cost of a run times the number of runs per month: a weekly schedule runs four or five times a month.
  • If you lack credits when a run is due, that run fails with “Not enough credits” and is not charged. The schedule continues: buy credits before the next run.
  • A schedule is disabled automatically if you can no longer run the application or if its parameters are no longer valid.

Team

The Team page lists the members of your organisation and the seats used by your subscription. Managers can Invite a colleague by email (they receive a link to set their password), resend an invitation or remove a member. The resources of a removed member are handed over to a manager.

API

Applications can be run from your scripts through the REST API, with the same rules and credits as in the web interface. A run is created as a draft, then started. Authenticate with an OAuth2 access token of your account, or with your username and password (curl -u). With a plan including API access, run details also return the technical output data.

# 1. Create a draft run (the data follows the application's form)
curl -X POST "https://test.mewiso.net/api/v2/applications/apps/<app-uuid>/runs/" \
  -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{"data": {...}}'

# 2. Start it: credits are charged at this step
curl -X POST "https://test.mewiso.net/api/v2/applications/runs/<run-uuid>/start/" \
  -H "Authorization: Bearer <token>"

# 3. Follow its status
curl "https://test.mewiso.net/api/v2/applications/runs/<run-uuid>/" -H "Authorization: Bearer <token>"

The application's form, as a JSON schema, is returned by https://test.mewiso.net/api/v2/applications/apps/<app-uuid>/.

AI assistants (MCP)

Mewiso provides an MCP (Model Context Protocol) server. Connect it to Claude or another AI assistant to search the catalogue, inspect datasets, maps and documents, list applications and run them in plain language. The assistant acts with your account: it sees what you see and its runs use your credits.

Server URL
https://test.mewiso.net/mcp
Transport
Streamable HTTP
Authentication
OAuth 2.0 with PKCE, without client secret
OAuth client ID
uNfBoUv7KrI8NoryqPDpLROrl6xmzMMEJvVuqA1C

On first use, your assistant opens a Mewiso sign-in page in the browser: sign in with your usual account and authorise the access.

Claude Code

claude mcp add --transport http --client-id uNfBoUv7KrI8NoryqPDpLROrl6xmzMMEJvVuqA1C \
  --callback-port 33418 mewiso https://test.mewiso.net/mcp

Then run /mcp in Claude Code, select mewiso and choose Authenticate. Add --scope user to the command to use the server in all your projects.

Claude (web and desktop apps)

  1. Open Settings › Connectors and click Add custom connector.
  2. Name it Mewiso and enter the URL https://test.mewiso.net/mcp.
  3. In Advanced settings, enter the OAuth client ID uNfBoUv7KrI8NoryqPDpLROrl6xmzMMEJvVuqA1C and leave the secret empty.
  4. Click Add, then Connect and sign in to Mewiso.

On Team and Enterprise plans, an organisation owner adds the connector once for all members.

Other tools

Any MCP client supporting Streamable HTTP and OAuth with a pre-registered client can connect (VS Code, Cursor, Codex…). Declare the server URL; when the client asks for an OAuth client ID, give the one above. Many tools accept a configuration such as:

{
  "mcpServers": {
    "mewiso": { "type": "http", "url": "https://test.mewiso.net/mcp" }
  }
}

The sign-in page only returns to addresses allowed by the platform (Claude, and Claude Code on port 33418). If your tool reports a redirect URI error, send us the address it uses so that we allow it.

Examples of requests

  • “List the Mewiso applications I can run and what they cost.”
  • “Find the datasets about flooding in the catalogue.”
  • “Run the application on this area for last month and tell me when it is finished.”

Need more help?

Read the frequently asked questions, write to us through the contact form or at contact@hetwa.fr.