SpikoIntegrations · Treasury

Connect Spiko to Well

Read Spiko bank accounts and their payment details into Well over the Well-hosted Spiko MCP server. Each account resolves with its IBAN, BIC, currency, and holder, ready to sit beside your other connected accounts.

What Well pulls from Spiko

Spiko feeds bank account, payment detail, document into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Spiko’s access.

From SpikoIn Well
Bank account
Workspace account
Payment detail
Payment instrument
Document
Workspace document
Spiko
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Spiko → Well

2 triggers from Spiko.

  • When a Spiko bank account is read

    Pulls the holder's Spiko bank account with IBAN, BIC, currency, and holder name.

    Trigger·Account
  • When a Spiko bank account's payment details are read

    Resolves the account IBAN from the same Spiko bank account record so a payment instrument can be matched.

    Trigger·Payment method

What Well does with your Spiko connection

Connect

Connect Spiko over OAuth (MCP DCR via Well): Well registers a client through Spiko's OAuth Dynamic Client Registration and you approve on Spiko's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings bank account, payment detail, and document in from Spiko through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Spiko entity into workspace account, payment instrument, and workspace document, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Spiko lands in the workspace as workspace account, payment instrument, and workspace document you can search, chart, and automate.

Questions Spiko unlocks

Ask in plain language. Well answers from your connected Spiko connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Spiko connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Spiko connection…

31 agent skills run on Spiko.

Each one answers a question from live Spiko data. The required ones return nothing until a source like it is connected.

Needs a source like Spiko

Runway

Know how many months of cash you have at your current burn, with both sides of the division shown.

Cash position

Know how much cash you hold right now, with the accounts counted and the ones left out both stated.

Cost structure

See where your company's money actually goes, no spreadsheets required.

Payment and invoice lookup

Find what payment settled an invoice, or catch every payment that never got one.

Burn rate

Know what you spend in an average month over a window you can see, with the months that carried no spend counted.

Cash forecast

See the settled month-end cash series and where the line goes from the last complete month.

Cash flow bridge

See how the month moved from opening cash to closing cash, with whatever does not reconcile named as its own step.

Missing supplier invoices

See which suppliers owe you paperwork, before your accountant asks.

Assign missing invoices

Put a name on every settled expense that still has no invoice.

Missing invoice sweep

Walk the whole month-end sweep in one prompt.

Close the books

Drive the month-end close from open to sent to your accounting tool.

Categorize your suppliers

Close the category gaps behind your spend before you close a month.

Board pack

The board numbers in one pass, each with its scope and its window stated.

Subscription spend

See what each scheduled supplier costs a month and a year, how it moved, and where your workspaces can save.

Subscription actions

Cancel a subscription, ask for a better price or contest a double debit, with your bank's facts in the email.

Personal spending

See what you spent on one thing this month, and how that compares to a usual month.

Unposted and blocked

See what in a month has not reached the ledger, and which pile each item sits in.

Check bank and books

Check that your bank and your books match, and re-run what missed rows.

Connect Spiko in three steps

  1. 01

    Authorise the Spiko MCP server

    Choose Spiko in Well's Connections panel. Well opens the Spiko MCP server through an OAuth flow proxied at Well's Spiko endpoint, registering a client via Dynamic Client Registration so there is no secret to paste; you approve the read access on the consent step.

    • AuthOAuth (MCP DCR)
    • MCP server/v1/mcps/spiko/mcp
    • TransactionsRoadmap, not read today
  2. 02

    Map your entities

    Well reads your Spiko bank accounts with holder, IBAN, BIC, and currency, plus the payment details tied to them and any exposed documents, mapping each into the workspace as a structured record.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    The bank accounts sit beside your other connected accounts for querying and matching. Account-level transactions are not read today (a cross-tool resolver is on the roadmap) and crypto-wallet reads are blocked, so only fiat bank-account data serves the account entity.

    • First syncstarts as soon as connect completes

The MCP handshake completes in about a minute. Bank accounts and payment details read on connect; transaction reads are a roadmap item, not live.

How Spiko stays secure with Well

Spiko connects through the Well-hosted MCP server with OAuth Dynamic Client Registration proxied at Well's Spiko endpoint, so Well never stores a Spiko secret. The grant is read-only and, by design, narrow: it serves bank-account and payment-detail data, while account-level transaction reads stay on the roadmap and Ethereum-wallet reads are blocked. The token reads fiat account data and nothing it could change in Spiko.

OAuth (MCP DCR via Well)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsapi.wellapp.ai/v1/mcps/spiko/mcp
  • Read Spiko records

    Resources the Spiko MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve bank account, payment detail, and document across your stack

    Match identifiers in Spiko against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Spiko records

    Not granted; Spiko is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Spiko passwords or session cookies

    Authentication runs through OAuth (MCP DCR via Well) tokens we never see.

    refused
Disconnect any time from Well settings or Spiko’s admin panel.

Frequently asked questions about Spiko and Well

How does Well connect to Spiko?

Pick Spiko in Well's Connections panel and authorise through the Well-hosted Spiko MCP server. The OAuth flow is proxied via Well's Spiko endpoint and uses Dynamic Client Registration, so you approve access on the consent step without pasting a key. Well registers itself and the read connection opens from there.

What does Well read from Spiko today?

Well reads your Spiko bank accounts (the holder, IBAN, BIC, and currency) and the payment details tied to them, plus any documents Spiko exposes, and brings each into the workspace as a structured record. The bank-account and payment-instrument data is what flows; that is the slice of Spiko this connector serves into Well.

Does Well pull Spiko transactions or crypto-wallet balances?

No. Account-level transaction reads are held back today, pending a cross-tool resolver that ties a transaction to the right account, so movements do not flow yet; bringing them in is on the roadmap. Ethereum-wallet account reads are blocked outright, so only fiat bank-account data serves the account entity. What you get is the bank-account and payment side, not a transaction feed or a wallet balance.

So what can I actually do with the Spiko data in Well?

You can see each Spiko bank account beside the rest of your connected accounts, with its IBAN, BIC, currency, and holder resolved, and use the payment details to match an instrument when reconciling against another source. Because the account is structured in the workspace, it sits in the same place you query your other banking relationships, ready for matching once transaction reads land.

How current is the Spiko account data Well holds?

Well reads Spiko over the MCP connection in the background and refreshes the bank-account and payment-detail records as they change on the Spiko side, with the first connect bringing in the current set. Querying works on what has synced. Spiko stays the source of truth; Well keeps a structured, read-only copy.

What unwinds if I disconnect Spiko?

Disconnect Spiko in Well and the MCP token is dropped, so Well stops reading your bank accounts and payment details immediately. The connection was read-only throughout, so there is nothing written to Spiko to reverse. The account records Well already mirrored stay queryable in your workspace until you ask Support to clear them.

Spiko

Ready to connect Spiko?

Connect once. Every bank account, payment detail, document from Spiko becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.